Skip to content

PR pipelines failing due to failing test #8804

Closed

Description

Screen Shot 2019-11-26 at 12 18 19

Seems to be failing on Linux and Mac (single workspace tests).
Blocks PRs.

Activity

  1. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on Nov 26, 2019
  2. DonJayamanne commented on Nov 26, 2019

    @DonJayamanne
    Author

    More failures in master
    Screen Shot 2019-11-26 at 12 59 39

  3. DonJayamanne commented on Nov 26, 2019

    @DonJayamanne
    Author

    New failures are cropping up, seem to be flaky (these didn't show up this morning).
    Screen Shot 2019-11-26 at 14 43 55

  4. ericsnowcurrently commented on Nov 26, 2019

    @ericsnowcurrently

    CI pipeline:

    mac/linux functional tests

    �[0m  1) FileSystem Utils
           getFileHash
             the returned hash changes with modification:
    
          �[31mAssertionError: expected '2bd760a784a3e788564b91e4508053a972beb6c2515f32187da80d3b005f6aa5c5966bb957852a404da8f485d205667d2bb81f74e3c1966d2dd7407e6e19ff31' to not equal '2bd760a784a3e788564b91e4508053a972beb6c2515f32187da80d3b005f6aa5c5966bb957852a404da8f485d205667d2bb81f74e3c1966d2dd7407e6e19ff31'�[0m
          �[32m+ expected�[0m �[31m- actual�[0m
    
    �[0m�[90m
          at Context.test (out/test/common/platform/filesystem.functional.test.js:380:41)
    �[0m
    �[0m  2) FileSystem Utils
           getFileHash
             the returned hash is unique:
    
          �[31mAssertionError: expected '2bd760a784a3e788564b91e4508053a972beb6c2515f32187da80d3b005f6aa5c5966bb957852a404da8f485d205667d2bb81f74e3c1966d2dd7407e6e19ff31' to not equal '2bd760a784a3e788564b91e4508053a972beb6c2515f32187da80d3b005f6aa5c5966bb957852a404da8f485d205667d2bb81f74e3c1966d2dd7407e6e19ff31'�[0m
          �[32m+ expected�[0m �[31m- actual�[0m
    
    �[0m�[90m
          at Context.test (out/test/common/platform/filesystem.functional.test.js:391:41)
    

    linux multi-workspace tests

    �[0m  1) Interpreters - Workspace VirtualEnv Service
           Detect Virtual Environment:
    �[0m�[31m     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/vsts/work/1/s/out/test/interpreters/locators/workspaceVirtualEnvService.test.js)�[0m�[90m
          at listOnTimeout (internal/timers.js:531:17)
          at processTimers (internal/timers.js:475:7)
    �[0m
    
    �[0m  2) Interpreters - Workspace VirtualEnv Service
           Detect a new Virtual Environment:
    �[0m�[31m     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/vsts/work/1/s/out/test/interpreters/locators/workspaceVirtualEnvService.test.js)�[0m�[90m
          at listOnTimeout (internal/timers.js:531:17)
          at processTimers (internal/timers.js:475:7)
    �[0m
    
    �[0m  3) Interpreters - Workspace VirtualEnv Service
           Detect a new Virtual Environment, and other workspace folder must not be affected (multiroot):
    �[0m�[31m     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/vsts/work/1/s/out/test/interpreters/locators/workspaceVirtualEnvService.test.js)�[0m�[90m
          at listOnTimeout (internal/timers.js:531:17)
          at processTimers (internal/timers.js:475:7)
    

    all single-workspace tests

    (not actually failing in AzDo)

    �[0m  1) Interpreters - Workspace VirtualEnv Service
           Detect Virtual Environment:
    �[0m�[31m     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (d:\a\1\s\out\test\interpreters\locators\workspaceVirtualEnvService.test.js)�[0m�[90m
          at listOnTimeout (internal/timers.js:531:17)
          at processTimers (internal/timers.js:475:7)
    �[0m
    �[0m  2) Interpreters - Workspace VirtualEnv Service
           Detect a new Virtual Environment:
    �[0m�[31m     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (d:\a\1\s\out\test\interpreters\locators\workspaceVirtualEnvService.test.js)�[0m�[90m
          at listOnTimeout (internal/timers.js:531:17)
          at processTimers (internal/timers.js:475:7)
    

    debugger tests

    seen sporadically, so might not be related

    �[0m  1) Resolving Environment Variables when Debugging
           "before each" hook for "Confirm basic environment variables exist when launched in external terminal":
    �[0m�[31m     Error: No matching bindings found for serviceIdentifier: Symbol(IFileSystem)�[0m�[90m
          at _validateActiveBindingCount (node_modules/inversify/lib/planning/planner.js:62:23)
          at _getActiveBindings (node_modules/inversify/lib/planning/planner.js:48:5)
          at _createSubRequests (node_modules/inversify/lib/planning/planner.js:91:26)
          at /home/vsts/work/1/s/node_modules/inversify/lib/planning/planner.js:115:17
          at Array.forEach (<anonymous>)
          at /home/vsts/work/1/s/node_modules/inversify/lib/planning/planner.js:114:26
          at Array.forEach (<anonymous>)
          at _createSubRequests (node_modules/inversify/lib/planning/planner.js:94:20)
          at Object.plan (node_modules/inversify/lib/planning/planner.js:136:9)
          at /home/vsts/work/1/s/node_modules/inversify/lib/container/container.js:318:37
          at Container._get (node_modules/inversify/lib/container/container.js:311:44)
          at Container.get (node_modules/inversify/lib/container/container.js:230:21)
          at ServiceContainer.get (out/client/ioc/container.js:28:89)
          at Context.<anonymous> (out/test/debugger/envVars.test.js:32:48)
    
  5. ericsnowcurrently commented on Nov 26, 2019

    @ericsnowcurrently

    https://dev.azure.com/ms/vscode-python/_build/results?buildId=51655

    all single workspace tests

    (only sporadically failing in AzDo)

    �[0m  1) Interpreters - Workspace VirtualEnv Service
           Detect Virtual Environment:
    �[0m�[31m     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/vsts/work/1/s/out/test/interpreters/locators/workspaceVirtualEnvService.test.js)�[0m�[90m
          at listOnTimeout (internal/timers.js:531:17)
          at processTimers (internal/timers.js:475:7)
    �[0m
    �[0m  2) Interpreters - Workspace VirtualEnv Service
           Detect a new Virtual Environment:
    �[0m�[31m     Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/vsts/work/1/s/out/test/interpreters/locators/workspaceVirtualEnvService.test.js)�[0m�[90m
          at listOnTimeout (internal/timers.js:531:17)
          at processTimers (internal/timers.js:475:7)
    

    mac single-workspace tests

    �[0m  1) FileSystem Utils
           getFileHash
             the returned hash changes with modification:
    
          �[31mAssertionError: expected '13ec09abc29fa2efcff7fa76ca05c05227083b313f33d6c4fa52bb6de3d2c904ab523b20a8fb4fc9233a60803f21f5ff7ac7e4abfcb8a6bc0e1232c86d777e97' to not equal '13ec09abc29fa2efcff7fa76ca05c05227083b313f33d6c4fa52bb6de3d2c904ab523b20a8fb4fc9233a60803f21f5ff7ac7e4abfcb8a6bc0e1232c86d777e97'�[0m
          �[32m+ expected�[0m �[31m- actual�[0m
    
    �[0m�[90m
          at Context.<anonymous> (out/test/common/platform/filesystem.functional.test.js:380:41)
    �[0m
    
    �[0m  2) FileSystem Utils
           getFileHash
             the returned hash is unique:
    
          �[31mAssertionError: expected '13ec09abc29fa2efcff7fa76ca05c05227083b313f33d6c4fa52bb6de3d2c904ab523b20a8fb4fc9233a60803f21f5ff7ac7e4abfcb8a6bc0e1232c86d777e97' to not equal '13ec09abc29fa2efcff7fa76ca05c05227083b313f33d6c4fa52bb6de3d2c904ab523b20a8fb4fc9233a60803f21f5ff7ac7e4abfcb8a6bc0e1232c86d777e97'�[0m
          �[32m+ expected�[0m �[31m- actual�[0m
    
    �[0m�[90m
          at Context.<anonymous> (out/test/common/platform/filesystem.functional.test.js:391:41)
    �[0m
    
    �[0m  3) FileSystem Utils
           getFiles
             mixed types:
    
          �[31mAssertionError: expected [ Array(4) ] to deeply equal [ Array(4) ]�[0m
          �[32m+ expected�[0m �[31m- actual�[0m
    
           [
             "/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pyvsc-fs-tests-1133t6P6YQ4baciz/x/y/z/scripts/data.json"
             "/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pyvsc-fs-tests-1133t6P6YQ4baciz/x/y/z/scripts/eggs.py"
             "/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pyvsc-fs-tests-1133t6P6YQ4baciz/x/y/z/scripts/spam.py"
          �[31m-  "/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pyvsc-fs-tests-1133t6P6YQ4baciz/x/y/z/scripts/spam.soc"�[0m
          �[32m+  "/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pyvsc-fs-tests-1133t6P6YQ4baciz/x/y/z/scripts/spam.sock"�[0m
           ]
          �[0m�[90m
          at Context.<anonymous> (out/test/common/platform/filesystem.test.js:358:51)
    
  6. ericsnowcurrently commented on Nov 27, 2019

    @ericsnowcurrently

    https://dev.azure.com/ms/vscode-python/_build/results?buildId=51793

    mac/windows functional tests

    �[0m  1) Raw FileSystem
           createWriteStream
             overwrites existing file:
    
          �[31mAssertionError: expected '' to equal 'line1\nline2\n'�[0m
          �[32m+ expected�[0m �[31m- actual�[0m
    
          �[32m+line1�[0m
          �[32m+line2�[0m
          �[0m�[90m
          at Context.test (out/test/common/platform/filesystem.functional.test.js:318:38)
    
  7. ericsnowcurrently commented on Nov 27, 2019

    @ericsnowcurrently

    I've created 2 issues (#8825 & #8826) to address fixing the tests.

  8. ericsnowcurrently commented on Nov 27, 2019

    @ericsnowcurrently

    https://dev.azure.com/ms/vscode-python/_build/results?buildId=51841

    Mac/Windows functional tests

    �[0m  1) Raw FileSystem
           "after each" hook for "returns the correct WriteStream":
    �[0m�[31m     Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\VSSADM~1\AppData\Local\Temp\pyvsc-fs-tests-4360VQGCfPGHgV5r\x\y\z'�[0m�[90m
          at Object.rmdirSync (fs.js:677:3)
          at _rmdirRecursiveSync (node_modules\tmp\lib\tmp.js:284:10)
          at Object._cleanupCallback [as removeCallback] (node_modules\tmp\lib\tmp.js:408:5)
          at FSFixture.cleanUp (out\test\common\platform\filesystem.functional.test.js:35:21)
          at Context.teardown (out\test\common\platform\filesystem.functional.test.js:149:19)
    �[0m
    �[0m  2) FileSystem Utils
           search
             found matches:
    
          �[31mAssertionError: expected [ Array(4) ] to deeply equal [ Array(4) ]�[0m
          �[32m+ expected�[0m �[31m- actual�[0m
    
           [
          �[31m-  "C:/Users/VSSADM~1/AppData/Local/Temp/pyvsc-fs-tests-4360YHCS5enZGrrV/x/y/z/spam.data"�[0m
          �[31m-  "C:/Users/VSSADM~1/AppData/Local/Temp/pyvsc-fs-tests-4360YHCS5enZGrrV/x/y/z/spam.py"�[0m
          �[31m-  "C:/Users/VSSADM~1/AppData/Local/Temp/pyvsc-fs-tests-4360YHCS5enZGrrV/x/y/z/spam.pyc"�[0m
          �[31m-  "C:/Users/VSSADM~1/AppData/Local/Temp/pyvsc-fs-tests-4360YHCS5enZGrrV/x/y/z/spam.so"�[0m
          �[32m+  "C:\\Users\\VSSADM~1\\AppData\\Local\\Temp\\pyvsc-fs-tests-4360YHCS5enZGrrV\\x\\y\\z\\spam.data"�[0m
          �[32m+  "C:\\Users\\VSSADM~1\\AppData\\Local\\Temp\\pyvsc-fs-tests-4360YHCS5enZGrrV\\x\\y\\z\\spam.py"�[0m
          �[32m+  "C:\\Users\\VSSADM~1\\AppData\\Local\\Temp\\pyvsc-fs-tests-4360YHCS5enZGrrV\\x\\y\\z\\spam.pyc"�[0m
          �[32m+  "C:\\Users\\VSSADM~1\\AppData\\Local\\Temp\\pyvsc-fs-tests-4360YHCS5enZGrrV\\x\\y\\z\\spam.so"�[0m
           ]
          �[0m�[90m
          at Context.test (out\test\common\platform\filesystem.functional.test.js:421:49)
    
  9. locked as resolved and limited conversation to collaborators on Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable bugregressionBug didn't exist in a previous release

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions