Skip to content

Terminal Activation tests are flaky #22264

@karthiknadig

Description

@karthiknadig

This test fails often and requires re-run. 

1) Activation of Environments in Terminal
       Should activate with virtualenv:

      Environment not activated
      + expected - actual

      -false
      +true
      
      at testActivation (out/test/common/terminals/environmentActivationProviders/terminalActivation.testvirtualenvs.js:75:74)
      at Context.<anonymous> (out/test/common/terminals/environmentActivationProviders/terminalActivation.testvirtualenvs.js:95:9)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-internalLabel for non-user facing issuesbugIssue identified by VS Code Team member as probable bugneeds PRReady to be worked on

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions