Skip to content
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.

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

fix: Increase timeout for npm-webpack-dev-server tests #22489

Merged
merged 1 commit into from
Jun 23, 2022

Conversation

BlueWinds
Copy link
Contributor

User facing changelog

No user facing changes.

Additional details

The system tests in sourceRelativeWebpackModules.spec.ts have been extremely flaky the past few days, to the point where it's more "consistent failure" than it is "flake".

It seems to be simply a timeout issue - the 10s we've allocated aren't enough to successfully yarn install all the dependencies for webpack5_wds4-react and similar system test projects.

While I'd very much like to rewrite these tests so as not to take so long, there's no quick solution here and it would probably involve changing how we install system test dependencies entirely (or mocking them out not to actually install), something beyond the scope of my efforts at the moment.

Therefore, timeout increase. Green builds are super important.

Steps to test

How has the user experience changed?

PR Tasks

  • Have tests been added/updated?
  • [n/a] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
  • [n/a] Has a PR for user-facing changes been opened in cypress-documentation?
  • [n/a] Have API changes been updated in the type definitions?

@BlueWinds BlueWinds requested a review from a team as a code owner June 23, 2022 17:35
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Jun 23, 2022

Thanks for taking the time to open a PR!

@BlueWinds
Copy link
Contributor Author

Because this change affects only one set of CI jobs, and they've passed cleanly on the first try (while completely failing today in many other branches), I'm going to merge this in without waiting for a completely green build so that I can move on and address other failing tests separately.

@BlueWinds BlueWinds merged commit 0fccc45 into develop Jun 23, 2022
@BlueWinds BlueWinds deleted the flake-npm-webpack-dev-server branch June 23, 2022 17:51
tgriesser added a commit that referenced this pull request Jun 24, 2022
…esser/CLOUD-577-spec-list-display-latest-runs-batching

* muaz/CLOUD-577-spec-list-display-latest-runs:
  fix: Update "Request Access" button state after requesting access (ACI) (#22499)
  feat: Support "Queued" latest run status (#22497)
  fix: remove ctx.cloud.reset in tests, handle infinite loop in stale results (#22483)
  chore: add reporter webpack to gulp watch script (#22386)
  fix: Increase timeout for npm-webpack-dev-server tests (#22489)
  fix: Time out unmatched prerequests in proxy to avoid leaking memory (#22462)
  fix: Sort results in findCrossOriginLogs test helper to deterministic (#22481)
  fix: memory leak caused by storing base64 encoded files recieved by CDP `Network.requestWillBeSent` (#22460)
  fix: Improve cross-origin cookie handling (#22320)
  feat: Add button to clear value from search fields (#22202)
  chore: Add test to verify settings panels are collapsed by default (#22382)
  fix: process_profiler follow up work for v10 (#22363)
  chore: Update Chrome (stable) to 103.0.5060.53 (#22441)
  refactor: use design system windicss config (#21503)
  chore: update readme logo (#22433)
  chore: Update Chrome (beta) to 103.0.5060.53 (#22351)
  chore: updating version (#22432)
  Trigger Build
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants