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

api.startstop and api.detach test failing: "ERROR: thread X should NOT be under DynamoRIO" #2246

Open
derekbruening opened this issue Feb 27, 2017 · 5 comments

Comments

@derekbruening
Copy link
Contributor

Xref #2068

I've never seen this test fail like this:

https://ci.appveyor.com/project/DynamoRIO/dynamorio/build/1.0.214/job/hwk44b43swkv08sn

====> FAILURE in debug-internal-32 <====
debug-internal-32: 215 tests passed, **** 3 tests failed, but ignoring 2 for i2145: ****
	code_api|api.detach 
ERROR: thread 7 should NOT be under DynamoRIO
all done: 150000 iters
@derekbruening
Copy link
Contributor Author

@fhahn
Copy link
Contributor

fhahn commented Apr 20, 2017

@toshipiazza
Copy link
Contributor

derekbruening added a commit that referenced this issue Aug 3, 2017
Unfortunately two failures are happening often enough that I'm adding them
to the #2145 list here: 32-bit api.detach #2246 and 64-bit drmgr-test #1369.
derekbruening added a commit that referenced this issue Aug 3, 2017
Unfortunately two failures are happening often enough that I'm adding them
to the #2145 list here: 32-bit api.detach #2246 and 64-bit drmgr-test #1369.
derekbruening added a commit that referenced this issue Oct 27, 2017
Marks api.detach and api.startstop as flaky as they have been failing
occasionally on Appveyor.

Issue: #2093, #2246, #2145
derekbruening added a commit that referenced this issue Oct 27, 2017
Marks api.detach and api.startstop as flaky as they have been failing
occasionally on Appveyor.

Issue: #2093, #2246, #2145
fhahn pushed a commit that referenced this issue Dec 4, 2017
Marks api.detach and api.startstop as flaky as they have been failing
occasionally on Appveyor.

Issue: #2093, #2246, #2145
@hgreving2304
Copy link

@derekbruening derekbruening changed the title api.detach test failing non-det api.detach test failing: "ERROR: thread X should NOT be under DynamoRIO" Dec 15, 2020
@derekbruening derekbruening changed the title api.detach test failing: "ERROR: thread X should NOT be under DynamoRIO" api.startstop and api.detach test failing: "ERROR: thread X should NOT be under DynamoRIO" Dec 15, 2020
@derekbruening
Copy link
Contributor Author

This is happening in every run on GA Server2016 now. For now these are on the ignore list. But given that this has happened on Linux (#2068, folded into here) we shouldn't consider this a Windows-only issue.

derekbruening added a commit that referenced this issue Dec 15, 2020
Updates the Windows CI ignore list bug numbers to reflect the
newly-filed individual issues.

Re-adds client.drwrap-test-detach to the ignore list for 32-bit.

Issue: #2246, #4616, #4617, #4618, #4619, #4621, #4622, #4131, #4058
derekbruening added a commit that referenced this issue Dec 15, 2020
Updates the Windows CI ignore list bug numbers to reflect the
newly-filed individual issues.

Re-adds client.drwrap-test-detach to the ignore list for 32-bit,
and adds histogram-offline to 64-bit (both were already there for
the other bitwidth).

Issue: #2246, #4616, #4617, #4618, #4619, #4621, #4622, #4131, #4058
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants