-
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
full_coverage_test is flaky on Windows and Linux #23848
Comments
I'll attempt to get a minidump to debug this (cannot repro on my own Windows VM). |
BUG=#23848 R=koda@google.com Review URL: https://codereview.chromium.org//1230113008 .
Recent crash in Linux: NOTE: This is reported as a runtime error, but the child VM process is actually crashing (exit status -6 on Linux, 3 on Windows). Seems we still have a non-Windows-specific issue with shutdown vs. concurrent sweep. Here are the stack traces: |
Hypothesis: the sweeper is re-awakened by some allocation late in the shutdown process. Will track it down and move the waiting and/or add NoSafepointScopes. (Longer-term, we need to revamp the "tasks" counter method to synchronize these things.) |
... and here's the allocation (why are we compiling classes during shutdown?): (gdb) bt |
maybe s/EnsureIsFinalized/is_finalized/? |
I don't think that's sufficient, it seems to rely on actually compiling things. I'll move it to an earlier point in the shutdown process; CL is in the works (although the issue is low-ish prio since it only happens with the flag). |
Fixed ee49289 |
standalone/full_coverage_test is failing flakily on win32 release since 868d2c6 Mon Jul 13 17:49:49 2015 -0700
It also fails on win64 release.
Marking it as flaky in tests/standalone/standalone.status.
This test is also using package:unittest, which the core tests in tests/core, tests/standalone/, tests/language, tests/compiler, and tests/lib (except async?) should not be dependent on.
It should be rewritten not to use it - not many changes are needed.
FAILED: none-vm-checked release_x64 standalone/full_coverage_test
Expected: Pass
Actual: RuntimeError
CommandOutput[vm]:
stdout:
unittest-suite-wait-for-done
FAIL: CoverageTests
Expected: <0>
Actual: <3>
package:unittest/src/simple_configuration.dart 128:34 SimpleConfiguration.onExpectFailure
package:unittest/src/simple_configuration.dart 24:13 _ExpectFailureHandler.fail
package:unittest/src/matcher/expect.dart 121:5 DefaultFailureHandler.failMatch
package:unittest/src/matcher/expect.dart 95:20 expect
tests\standalone\full_coverage_test.dart 96:5 generateCoverage
tests\standalone\full_coverage_test.dart 219:5 main.
package:unittest/src/internal_test_case.dart 120:37 InternalTestCase.run.
....
@fsc8000 @mlippautz @kodandersson
The text was updated successfully, but these errors were encountered: