-
Notifications
You must be signed in to change notification settings - Fork 81
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
FuzzMessageDecode
fails sometimes
#3316
Comments
It doesn't help, it just tells that this problem is poorly reproduceable.
Hardly ever it can be related to the logger sync. |
as we had data races in pkg/network tests it seems to me that failing FuzzMessageDecode with |
Discussed, and closing this issue as not relevant after #3307. |
Reproduced on fresh 37d4012 (#791, Ubuntu 22.04, https://github.com/nspcc-dev/neo-go/actions/runs/8277371374/job/22647600402?pr=3355), but the real reason is not in FuzzMessageDecode, because race is detected in the other test:
But somehow FuzzMessageDecode also fails with no reason, I think that it's just about the fact that race from previous test is detected during FuzzMessageDecode run.
Full logs: |
I thought fuzzers are disabled in our regular runs. |
It's just about the fact that seed corpus of this test is quite large. But we run our tests without |
Nested goroutines could cause logging race. Close #3316 Signed-off-by: Ekaterina Pavlova <[email protected]>
Nested goroutines could cause logging race. Close #3316 Signed-off-by: Ekaterina Pavlova <[email protected]>
Run tests (ubuntu-20.04, 1.20) and ubuntu 1.19
5_Run tests.txt
maybe related to #3307 (or caused by).
Just rerunning the failed job helps - for example Run tests (ubuntu-20.04, 1.20) (just successful run).
The text was updated successfully, but these errors were encountered: