Skip to content

Fix test failures due to linting. #20612

@karthiknadig

Description

@karthiknadig
1) Multiroot Linting
       Enabling Pylint in root and also in Workspace, should return errors:

      AssertionError [ERR_ASSERTION]: No errors returned by linter
      + expected - actual

      -false
      +true
      
      at testLinterInWorkspaceFolder (out/test/linters/lint.multiroot.test.js:64:16)
      at runTest (out/test/linters/lint.multiroot.test.js:107:9)
      at Context.<anonymous> (out/test/linters/lint.multiroot.test.js:70:9)

  2) Multiroot Linting
       Disabling Pylint in root and enabling in Workspace, should return errors:

      AssertionError [ERR_ASSERTION]: No errors returned by linter
      + expected - actual

      -false
      +true
      
      at testLinterInWorkspaceFolder (out/test/linters/lint.multiroot.test.js:64:16)
      at runTest (out/test/linters/lint.multiroot.test.js:107:9)
      at Context.<anonymous> (out/test/linters/lint.multiroot.test.js:80:9)

  3) Multiroot Linting
       Enabling Flake8 in root and also in Workspace, should return errors:

      AssertionError [ERR_ASSERTION]: No errors returned by linter
      + expected - actual

      -false
      +true
      
      at testLinterInWorkspaceFolder (out/test/linters/lint.multiroot.test.js:64:16)
      at runTest (out/test/linters/lint.multiroot.test.js:107:9)
      at Context.<anonymous> (out/test/linters/lint.multiroot.test.js:87:9)

  4) Multiroot Linting
       Disabling Flake8 in root and enabling in Workspace, should return errors:

      AssertionError [ERR_ASSERTION]: No errors returned by linter
      + expected - actual

      -false
      +true
      
      at testLinterInWorkspaceFolder (out/test/linters/lint.multiroot.test.js:64:16)
      at runTest (out/test/linters/lint.multiroot.test.js:107:9)
      at Context.<anonymous> (out/test/linters/lint.multiroot.test.js:97:9)

Metadata

Metadata

Assignees

Labels

area-internalLabel for non-user facing issuesbugIssue identified by VS Code Team member as probable bugimportantIssue identified as high-priorityneeds PRReady to be worked onverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions