-
Notifications
You must be signed in to change notification settings - Fork 351
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
Investigate the tests race conditions #1369
Comments
one of the race conditions appears to be caused by the changes introduced in #1300. Now we're reading the header in the CheckTxState in Baseapp during ProcessProposal, which is somehow tripping up the race detector since that same state can be written to by a different routine, although that different routine doesn't appear to doing so until we commit the block. |
We could add a mutex to the context to fix this, no?. But another race sometimes happens also, related to IAVL (would need to run the tests multiple times to get it) |
we should see what the cosmos-sdk does to prevent this in v0.47.0-rc2 |
Posting here a recent race we observed in our CI.
|
Capturing recent occurrence
|
@MSevey Can you please link where this happened? |
this issue came up when in my 1:1 with Evan. I just rand the Full stack trace https://gist.github.com/MSevey/e9a5db50e5407ee6c8810471659b0daa |
we should try again since this should at least help celestiaorg/cosmos-sdk#326 since it eliminates the reading of the header in the checkTx state during prepare and process proposal |
One more. Maybe related to above, maybe not:
|
…2163) ## Overview the testnode is still hitting the race detector #1369, so we aren't running those integration tests with the race detector ## Checklist - [x] New and updated code has appropriate documentation - [x] New and updated code has new and/or updated testing - [x] Required CI checks are passing - [x] Visual proof for any user facing features like CLI or documentation updates - [ ] Linked issues closed with keywords
…2163) ## Overview the testnode is still hitting the race detector #1369, so we aren't running those integration tests with the race detector ## Checklist - [x] New and updated code has appropriate documentation - [x] New and updated code has new and/or updated testing - [x] Required CI checks are passing - [x] Visual proof for any user facing features like CLI or documentation updates - [ ] Linked issues closed with keywords
…2163) ## Overview the testnode is still hitting the race detector #1369, so we aren't running those integration tests with the race detector ## Checklist - [x] New and updated code has appropriate documentation - [x] New and updated code has new and/or updated testing - [x] Required CI checks are passing - [x] Visual proof for any user facing features like CLI or documentation updates - [ ] Linked issues closed with keywords
blocked by first switching to v0.50.0 of the sdk since that would likely fix this issue #3535 |
Description
Currently, when running the race tests, we're also adding the
-short
flag. This means that multiple tests get skipped and not checked for races:celestia-app/Makefile
Line 113 in 6163e27
To see the races happening, run the following:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: