diff options
author | fanquake <fanquake@gmail.com> | 2022-02-21 13:09:43 +0000 |
---|---|---|
committer | fanquake <fanquake@gmail.com> | 2022-02-21 13:12:36 +0000 |
commit | 2ab4fbe375571fb8f102c35841e6dc9fb670d5b7 (patch) | |
tree | 42d2b4d7b7218806613686c91eb874ff196f4b72 /contrib/devtools/README.md | |
parent | 1337b93f50d9874fa3bce7c0b5bb141aad9b1c49 (diff) | |
parent | fa27745ccbdf8df7949a2e79dba18de49dc89169 (diff) | |
download | bitcoin-2ab4fbe375571fb8f102c35841e6dc9fb670d5b7.tar.xz |
Merge bitcoin/bitcoin#24292: Revert "ci: Run fuzzer task for the master branch only"
fa27745ccbdf8df7949a2e79dba18de49dc89169 ci: Bump fuzz tasks to jammy (MarcoFalke)
fab8cd5f8764883dc48695c0e0916bae42f1cfdc Revert "ci: Run fuzzer task for the master branch only" (MarcoFalke)
Pull request description:
This reverts commit 5a9e255e5a324e7aa0b63a9634aa3cfda9a300bd.
I think we should attempt to maintain the fuzz tasks for release branches as well.
If it is too difficult for one branch, it could make sense to disable it for that branch, but not for all branches unconditionally.
Also, bump to jammy.
ACKs for top commit:
fanquake:
ACK fa27745ccbdf8df7949a2e79dba18de49dc89169 - we'll see how we go with the 23.x release branch.
Tree-SHA512: d6d08e7dce0884b556c51ff1896aebbbb5a805c22decd58af81a04192d19876978696017b489ec55886ddfd5c022963baaab5f11022369ae5291016826ff8017
Diffstat (limited to 'contrib/devtools/README.md')
0 files changed, 0 insertions, 0 deletions