-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Unresolvable URL error flakily provides crazy message #9503
Comments
It looks like fail_gracefully_on_url_resolve_test isn't marked flaky yet - Nathan or Bob, can you please do this asap? cc @munificent. |
I'm on it! |
Sorry about that, I put out a CL for this last night but forgot to commit. |
I just realized this had no owner. Mads, are you the right person for this? Set owner to @madsager. |
Have this bees seen recently? I have not been able to reproduce it. I have been running the test for several hours using the script below (on a English Windows) without seeing any errors. Also grepping the flaky-log on the Russian buildbot this does not show up for the last 100 runs. import 'dart:io'; void run() { void main() { |
No, I haven't seen it or been able to repro it either. |
Removed from status file in https://code.google.com/p/dart/source/detail?r=22327. Added AssumedStale label. |
Removed Area-IO label. |
On the pub-win-russian bot, we saw the following failure in pub/install/hosted/fail_gracefully_on_url_resolve_test: http://build.chromium.org/p/client.dart/builders/pub-win-russian/builds/1654/steps/pub%20tests%20failures/logs/stdio
For posterity, dart:io is reporting an error with the following error message:
OS Error: �1KG=> - MB> 2@5<5==0O >H81:0, 2>7=8:0NI0O 2> 2@5<O @07@5H5=8O 8<5=8 C7;0, 8 >7=0G0NI0O, GB> ;>:0;L=K9 A5@25@ =5 ?>;CG8; >B25B0 >B ?>;=><>G=>3> A5@25@0.
It looks like it's just reading from some random block of memory. This seems to be happening flakily, and so far we've only seen it on Windows.
This is a pretty serious bug, and it's also forcing us to mark fail_gracefully_on_url_resolve_test as flaky.
The text was updated successfully, but these errors were encountered: