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
co19 spawnUri and spawn tests broken #15974
Comments
Slow == forever in this case. The error from the isolate is not forwarded to the spawning isolate. There is a mismatch in expectations about the future completing without errors. |
Added Library-Async label. |
Looking at this, these tests seem broken. Normally, if you use extra files, the test framework expects them to be listed with a // OtherScripts= The other tests seem to be testing for an arbitrary exception, so anything that goes wrong (including file not found) counts as passing for the tests that are verifying for errors. cc @whesse. |
Oops, the reason A01_t01 was passing on Dartium and dart2js was because it was listed as Fail there. |
Issue #13992 has been merged into this issue. cc @ricowind. |
To clarify the status of these tests: They aren't copying the additional files they need to the generated test directories. To fix this, requires filing a co19 bug. |
Here are some more tests that are timing out on the VM, but not on dart2js: Skipping them in the co19-runtime.status file. |
2019 update:
Build configurations for reliably failing
Build configurations for flaky
Build configurations for reliably failing or flaky (skipped)
|
Couple notes:
|
@sigmundch Thanks! This leaves two reliably failing
And one flaky
|
The following tests are running very slowly on our test bots (e.g., 1 min each on the dartium-linux bots). I am marking them skipped for Dartium and the standalone VM as they significantly impact the overall bot cycle times.
LibTest/isolate/Isolate/spawnUri_A01_t02
LibTest/isolate/Isolate/spawnUri_A01_t03
LibTest/isolate/Isolate/spawnUri_A02_t02
LibTest/isolate/Isolate/spawnUri_A02_t03
LibTest/isolate/Isolate/spawnUri_A02_t04
The text was updated successfully, but these errors were encountered: