Skip to content

Improve and fix remote integration test suite #147755

Open

Description

From #147376

We found a few issues:

  • There are real differences between test-remote-integration.sh and test-remote-integration.bat. One of them is the amount of extensions being built.
  • In our CI, those extensions keep getting built all over again. First by the Electron integration tests, then by the Web integration tests, then by the Remote integration tests. It seems very wasteful.
  • ‼️ While it appears at first glace that the suite runs much faster on Windows than macOS, you quickly realise that the tests are actually failing but the build reports them as having passed. On Windows, they fail quite early and a bunch of test suites never even run. On macOS, scroll to the end and you'll also see that they fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

debtCode quality issuesengineeringVS Code - Build / issue tracking / etc.importantIssue identified as high-priorityremoteRemote system operations issues

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions