-
Notifications
You must be signed in to change notification settings - Fork 562
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
HANG burst_threads test failing (non-det) #2092
Comments
Actually the gdb instance above was instead a bug in #2089. The CDash hang was in TOT though and the mentioned race seems like an actual possibility. |
This test has also failed on Travis. Here's on but there have been others: https://travis-ci.org/DynamoRIO/dynamorio/jobs/350115271 |
OK that Travis failure is an output mismatch: one core has 0 data refs and doesn't print the string "Miss rate". |
Allows for zero data or instruction refs on a core and thus no printed miss rate, to reduce flakiness in the burst_threads test. Issue: #2092
Allows for zero data or instruction refs on a core and thus no printed miss rate, to reduce flakiness in the burst_threads test. Issue: #2092
It also just failed on Travis on #3058 with:
|
Xref #2941 |
Xref #2694 |
I ran into this on glinux (rare!) <Application |
I've tested >>1000 times all 32-bit/64bit debug+release and could not reproduce any failure. There were a few fixes lately around the line above, closing. |
Seen on CDash: http://dynamorio.org/CDash/buildSummary.php?buildid=15334
I managed to get a local repro into gdb:
I suspect that it's a race where an app thread exits after DR constructs a
list of app threads but before DR synchs with each one.
The text was updated successfully, but these errors were encountered: