Skip to content
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

Merged
merged 3 commits into from
Apr 15, 2020
Merged

Conversation

maflcko
Copy link
Member

@maflcko maflcko commented Apr 8, 2020

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

@fanquake fanquake added the Tests label Apr 8, 2020
@DrahtBot
Copy link
Contributor

DrahtBot commented Apr 9, 2020

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, 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.

@practicalswift
Copy link
Contributor

Concept ACK

Thanks for doing this: faster fuzzing is better fuzzing.

@maflcko maflcko force-pushed the 2004-testLogExtraArgs branch from f5d6a22 to 18a9987 Compare April 15, 2020 15:05
@maflcko maflcko force-pushed the 2004-testLogExtraArgs branch from 18a9987 to faea0a9 Compare April 15, 2020 19:06
@maflcko
Copy link
Member Author

maflcko commented Apr 15, 2020

Rebased now that #18615 is merged

@maflcko maflcko force-pushed the 2004-testLogExtraArgs branch from faea0a9 to fa69f88 Compare April 15, 2020 19:13
@practicalswift
Copy link
Contributor

ACK fa69f88 -- patch looks correct

@maflcko
Copy link
Member Author

maflcko commented Apr 15, 2020

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.

@maflcko maflcko merged commit 5447097 into bitcoin:master Apr 15, 2020
@maflcko maflcko deleted the 2004-testLogExtraArgs branch April 15, 2020 23:44
@ryanofsky ryanofsky mentioned this pull request Jun 4, 2020
deadalnix pushed a commit to Bitcoin-ABC/bitcoin-abc that referenced this pull request Jun 29, 2020
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
Fabcien pushed a commit to Bitcoin-ABC/bitcoin-abc that referenced this pull request Dec 9, 2020
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
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Feb 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants