Skip to content

Figure out why "Interpreters - Workspace VirtualEnv Service" timeout is so high. #13126

@ericsnowcurrently

Description

@ericsnowcurrently

In #12833 we noted how PR #12795 resulted in some CI test failures. Basically, one specific set of tests in one specific configuration started timing out:

  • only 2 tests in "Interpreters - Workspace VirtualEnv Service" were affected
  • only "Py3x Multi Workspace" (locally also "Py3x Single Workspace")
  • only on linux (locally also on Windows)

PR #13098 changed the timeout on CI from 60s to 120s (non-CI 15s to 30s). This fixed the problem locally but we still saw some of the same failures. So the timeout might not be the issue. I also saw the same failures before #12795.

Looking at the logs, the time that the tests are taking (and the extension takes to initialize) hasn't really changed much. So something else is going on. We need to figure out what, in case there is an underlying problem in the extension that might affect users.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-internalLabel for non-user facing issuesdebtCovers everything internal: CI, testing, refactoring of the codebase, etc.needs spikeLabel for issues that need investigation before they can be worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions