-
Notifications
You must be signed in to change notification settings - Fork 340
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
Flaky Test: solana-core banking_stage::consumer::tests::test_write_persist_transaction_status #4853
Comments
Running this test with tsan shows there is a data race. SUMMARY: ThreadSanitizer: data race /home/sol/.cargo/registry/src/index.crates.io-6f17d22bba15001f/librocksdb-sys-0.16.0+8.10.0/rocksdb/logging/env_logger.h:143:14 in rocksdb::EnvLogger::Logv(char const*, __va_list_tag*)
|
We should first revert the change that caused this regression rather than keeping it in master while we work on a fix |
In hindsight, yeah, we should probably have. In this specific case, I believe I have root-caused it and have a fix so it would be more work to revert and then push back in For the general case, yes, I'd agree that we should be more aggressive about backing changes out that make CI flaky |
Revert is here: #4875 |
See you at the finish line #4873 😉 ![]() |
Please do not use rayon::spawn without manually joining, those threads are impossible to keep accounted for (e.g.to ensure they finish in a reasonable time), especially on a global rayon pool. |
AUTO-GENERATED. DO NOT EDIT.
📝 Buildkite Analytics
The text was updated successfully, but these errors were encountered: