-
Notifications
You must be signed in to change notification settings - Fork 38.7k
fuzz: Disable debug log file #18571
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
fuzz: Disable debug log file #18571
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
fae06f8 to
facc7e5
Compare
ead5571 to
f5d6a22
Compare
|
Concept ACK Thanks for doing this: faster fuzzing is better fuzzing. |
f5d6a22 to
18a9987
Compare
18a9987 to
faea0a9
Compare
|
Rebased now that #18615 is merged |
faea0a9 to
fa69f88
Compare
|
ACK fa69f88 -- patch looks correct |
|
I couldn't verify my claim that this speeds up fuzzing, but at least I am no longer running out of disk space, so I think it is still required. |
Summary: This will allow for the scheduler to be destructed even for tests that only use the `BasicTestingSetup`. This fixes a TSAN lock order inversion issue when running the `reverselock_tests` and the `scheduler_tests` together. Extracted from core [[bitcoin/bitcoin#18571 | PR18571]]. Test Plan: ./src/test/test_bitcoin -t reverselock_tests,scheduler_tests ninja check Reviewers: #bitcoin_abc, deadalnix, jasonbcox Reviewed By: #bitcoin_abc, deadalnix, jasonbcox Differential Revision: https://reviews.bitcoinabc.org/D6766
Summary:
```
There are several issues with writing to a debug log file when fuzzing:
Disk access is slow, but fuzzing should be fast (Note: I could not
verify this claim with data)
Disks have a limited size and will eventually run out of space, but
fuzzing should run continuous
Fix both issues by disabling the debug log file for fuzz tests
```
Backport of core [[bitcoin/bitcoin#18571 | PR18571]].
Depends on D8636.
Test Plan:
ninja all check
ninja bitcoin-fuzzers
./test/fuzz/test_runner.py <path_to_corpus>
Reviewers: #bitcoin_abc, deadalnix
Reviewed By: #bitcoin_abc, deadalnix
Differential Revision: https://reviews.bitcoinabc.org/D8637
There are several issues with writing to a debug log file when fuzzing:
Fix both issues by disabling the debug log file for fuzz tests