-
Notifications
You must be signed in to change notification settings - Fork 214
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
[SEVERE] test_api v0.4.6 causes "Timed out waiting for Chrome to connect." #1620
Comments
Just to highlight for investigation:I speculate that this is where the bug was introduced: https://github.com/dart-lang/test/blob/master/pkgs/test_core/lib/src/runner.dart#L261 I can't confirm it yet, but it's one of the significant changes from 0.4.5 to 0.4.6. |
I have the same exact error. All my browser tests cases started to fail |
Same here.
|
Browser tests are definitely broken! The title should have a "SEVERE" prefix. |
same for https://github.com/getsentry/sentry-dart/runs/3984790347?check_suite_focus=true
is a workaround |
This also affects dart-lang packages, e.g.: |
Ah yes, looks like I got hit by dart-lang/pub#3126 again :(. We need to commit a local .pubignore or something to prevent this in the future until a fix is out for the pub validator :(. |
This should be fixed in |
Running
dart run build_runner test --fail-on-severe
withtest_api
0.4.5 consistently runs the tests within 2-3 seconds whereastest_api
0.4.6 consistently exceeds the 30s timeout with:Adding:
Resolves the timeouts.
Tests Failing with timeout: https://github.com/felangel/bloc/runs/3982800253
Commit with fix: felangel/bloc@fc591f6
Tests Passing: https://github.com/felangel/bloc/runs/3982912418
Related Issues:
I'm guessing the bug was introduced in #1604 but I'm not totally sure.
Originally posted by @felangel in #1610 (comment)
The text was updated successfully, but these errors were encountered: