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
Web hot restart tests flaky timeout frequently causing web_tool_tests
failure
#85043
Comments
* Update hot_reload_web_test.dart For #85043 * Add missing import
Windows web_tool_tests
2.74% flaky
|
looking in the logs I see some canvaskit errors. ill switch the apps to use html |
Windows web_tool_tests
2.74% flakyWindows web_tool_tests
2.74% flaky
@yjbanov ptal |
Windows web_tool_tests
2.74% flakyweb_tool_tests
failure
The test failed on the head-head-head bot today in the following way:
|
@alexmarkov could you please share a link to the failure? I am only seeing engine tests failing currently... |
Looks like the HHH bot is fine now, so the issue seems to be intermittent. Created a separate issue to investigate (above). |
@annagrin Would you mind taking this issue? This is outside my domain expertise. |
The failing test is "hot_reload_web_test.dart: newly added code executes during hot restart - canvaskit" This one should still be disabled since the flakiness is caused by downloading canvaskit over the network |
Current flaky ratio for the past 15 days is 0.63%. |
My understanding is that the current status of this is that it is waiting for the canvaskit pin to re-enable the disabled test. Dropping priority based on that. |
@zanderso Looks like this issue bundles a few issues together - hot restart hangs, errors on connection to chrome, and canvaskit binding errors. I enabled two tests in packages/flutter_tools/test/web.shard/hot_reload_web_test.dart but it looks like one of them is still failing due to canvaskit issue. Thanks for disabling it! I'll keep monitoring this issue to see if my fix stops flakiness due to hot restart hangs. |
Current flaky ratio for the past 15 days is 0.56%. |
Current flaky ratio for the past 15 days is 0.00%. |
1 similar comment
Current flaky ratio for the past 15 days is 0.00%. |
Current flaky ratio for the past 15 days is 0.76%. |
A new flake - looks like we are not retrying when connecting to a chrome tab:
/cc @jonahwilliams I think we could just pass a |
Current flaky ratio for the past 15 days is 0.57%. |
@annagrin I'm not sure @jonahwilliams is reading here anymore if that question was directed at him. If a retry there could succeed after an initial failure, then that sounds like something that could deflake the test. |
Current flaky ratio for the past 15 days is 0.00%. |
@zanderso I will add the retries to see if it has any effect, but it looks like the occurrences are pretty rare at the moment. |
Current flaky ratio for the past 15 days is 0.00%. |
1 similar comment
Current flaky ratio for the past 15 days is 0.00%. |
Closing this as there have been no flakiness for a month, please feel free to reopen if needed! |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
See https://ci.chromium.org/p/flutter/builders/prod/Windows%20web_tool_tests
In particular:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8843718898922094865/+/u/run_test.dart_for_web_tool_tests_shard_and_subshard_web/stdout?format=raw
It looks like this started happening with an Engine roll containing only a Fuchsia SDK roll, so it is probably unrelated.
/cc @yjbanov @shihaohong
The text was updated successfully, but these errors were encountered: