[go: nahoru, domu]

Skip to content
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

Win64 flaky test failure vm/cc/TimelineAnalysis_ThreadBlockCount #25091

Closed
fsc8000 opened this issue Dec 2, 2015 · 1 comment
Closed

Win64 flaky test failure vm/cc/TimelineAnalysis_ThreadBlockCount #25091

fsc8000 opened this issue Dec 2, 2015 · 1 comment
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.

Comments

@fsc8000
Copy link
Contributor
fsc8000 commented Dec 2, 2015

@johnmccutchan

http://build.chromium.org/p/client.dart/builders/vm-win64-release-be/builds/9124/steps/checked_tests/logs/stdio

=== Failure summary:

FAILED: none-vm-checked release_x64 vm/cc/TimelineAnalysis_ThreadBlockCount
Expected: Pass
Actual: Fail
CommandOutput[run_vm_unittest]:

stdout:
Running test: TimelineAnalysis_ThreadBlockCount
Done: TimelineAnalysis_ThreadBlockCount

stderr:
vm\timeline_test.cc:383: error: expected: <00000000006F8620> but was: <00000000006FAC40>
vm\timeline_test.cc:384: error: expected: <00000000006FAC40> but was: <00000000006F8620>
vm\timeline_test.cc:406: error: expected: LabelMatch(it.Next(), "B1")
vm\timeline_test.cc:408: error: expected: LabelMatch(it.Next(), "B2")
vm\timeline_test.cc:410: error: expected: LabelMatch(it.Next(), "B3")
vm\timeline_test.cc:412: error: expected: LabelMatch(it.Next(), "A1")

Command[run_vm_unittest]: set DART_CONFIGURATION=ReleaseX64 & build\ReleaseX64\run_vm_tests --ignore-unrecognized-flags TimelineAnalysis_ThreadBlockCount
Took 0:00:00.033000

Short reproduction command (experimental):
python tools/test.py -mrelease --write-debug-log --write-test-outcome-log --copy-coredumps --exclude-suite pkg --checked -t60 vm/cc/TimelineAnalysis_ThreadBlockCount

=== 1 test failed

@fsc8000 fsc8000 added the area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. label Dec 2, 2015
@johnmccutchan johnmccutchan self-assigned this Dec 12, 2015
@johnmccutchan
Copy link
Contributor

I believe this was fixed by waiting for 32 milliseconds instead of 1 millisecond. On Windows a sleep of 1 millisecond may be a no-op.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
Projects
None yet
Development

No branches or pull requests

2 participants