-
Notifications
You must be signed in to change notification settings - Fork 77
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
Race detected during TestRegisterCandidate #2868
Comments
Preventing data race during test with mutex in testAct. Close #2868 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
Preventing data race during test with mutex in testAct. Close #2868 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
Preventing data race during test with mutex in testAct. Close #2868 Signed-off-by: Ekaterina Pavlova <ekt@morphbits.io>
#3110 may be closely related to this issue. We need to ensure that this bug still exists after #3110 fix (@AliceInHunterland, you may search through our failing test logs in the https://github.com/nspcc-dev/neo-go/actions/workflows/tests.yml). |
@AnnaShaleva it seems that logs of jobs before #3110 are unavailable (example https://github.com/nspcc-dev/neo-go/actions/runs/6459577009/job/17535640232 ), locally with git checkout 96449d8^ TestRegisterCandidate is non-reproducible and here too (https://github.com/nspcc-dev/neo-go/actions/runs/7797187985/job/21263311972?pr=3304). |
None of these issues are reproduced reliably, so we can fix things we can and know how to fix and then see if any of the rest reproduce in like a month. |
Check out several recently failing tests (5-10 jobs) those logs are still available at https://github.com/nspcc-dev/neo-go/actions/workflows/tests.yml. Any failing job is suit, because we haven't change the logic of this test for quite a long time. If this issue is not reproduced, then I suppose that the problem was solved by native cache refactoring in #3110. |
OK, after discussion the result is the following: latest failing testing jobs do not contain failing TestRegisterCandidate test. I think, that this problem was solved by Neo cache refactoring and I'd suggest to close this issue as completed if no TestRegisterCandidate failures discovered in the nearest future. |
It's likely to be the test's issue, but we'd better ensure that everything is OK with native cache handling.
The text was updated successfully, but these errors were encountered: