Skip to content

Broken canary tests #7806

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
lforst opened this issue Apr 11, 2023 · 0 comments · Fixed by #7805
Closed

Broken canary tests #7806

lforst opened this issue Apr 11, 2023 · 0 comments · Fixed by #7805
Assignees
@lforst
Labels
Type: Tests

Comments

@lforst
Copy link
Contributor

lforst commented Apr 11, 2023 •
edited
Loading

Canary tests are horribly broken since we parallelized our E2E tests.

This is probably due to multiple reasons:

  • Running multiple yarn installs at the same time corrupts the yarn cache for some reason
  • Our port assigning logic assigns the same ports for multiple canary tests
  • Timeouts due to the runner being overwhelmed by too many processes being started
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lforst lforst

Labels
Type: Tests
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(e2e): Fix various issues with concurrent E2E and Canary tests getsentry/sentry-javascript
1 participant
@lforst