Skip to content

Conversation

hebasto
Copy link
Member

@hebasto hebasto commented Aug 17, 2021

It is a demo for #22730 in the 22.x branch. Fuzz tests must not run here.

@hebasto
Copy link
Member Author

hebasto commented Aug 18, 2021

Updated according to #22730 (comment).

@hebasto hebasto force-pushed the 210817-22.0-ci-fuzz branch 3 times, most recently from c68e614 to 63c6315 Compare August 18, 2021 16:26
@hebasto hebasto force-pushed the 210817-22.0-ci-fuzz branch from 63c6315 to 085b678 Compare August 18, 2021 17:20
@fanquake fanquake closed this Aug 20, 2021
fanquake added a commit that referenced this pull request Aug 20, 2021
5a9e255 ci: Run fuzzer task for the master branch only (Hennadii Stepanov)

Pull request description:

  #22629 (comment):
  > I think we need to decide whether running the fuzzer CI in any branch other than master is something we want to be doing / maintaining. This seems pretty unsustainable unless we at least make changes in regards to the fuzz inputs being used by the different branches. I'm pretty sure Marco has mentioned this before.

  This PR makes CI ignore fuzz tests by forcing `RUN_FUZZ_TESTS=false` for all cases when it is not the master branch or a PR based on it.

  See #22731 as a demo for the 22.x branch.

ACKs for top commit:
  MarcoFalke:
    cr ACK 5a9e255 no opinion on the concept, also didn't test
  fanquake:
    ACK 5a9e255 - didn't test other than to look at #22731.

Tree-SHA512: 48f8f02f1814d4f15293a8804b76d544a08784ea7acd930b5c6d4608564d30aa5a608b1a511386ffda6975feec700c1bbeb86a30a75a7e48a1c5b167a227dbdd
@hebasto hebasto deleted the 210817-22.0-ci-fuzz branch August 20, 2021 07:29
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Aug 20, 2021
5a9e255 ci: Run fuzzer task for the master branch only (Hennadii Stepanov)

Pull request description:

  bitcoin#22629 (comment):
  > I think we need to decide whether running the fuzzer CI in any branch other than master is something we want to be doing / maintaining. This seems pretty unsustainable unless we at least make changes in regards to the fuzz inputs being used by the different branches. I'm pretty sure Marco has mentioned this before.

  This PR makes CI ignore fuzz tests by forcing `RUN_FUZZ_TESTS=false` for all cases when it is not the master branch or a PR based on it.

  See bitcoin#22731 as a demo for the 22.x branch.

ACKs for top commit:
  MarcoFalke:
    cr ACK 5a9e255 no opinion on the concept, also didn't test
  fanquake:
    ACK 5a9e255 - didn't test other than to look at bitcoin#22731.

Tree-SHA512: 48f8f02f1814d4f15293a8804b76d544a08784ea7acd930b5c6d4608564d30aa5a608b1a511386ffda6975feec700c1bbeb86a30a75a7e48a1c5b167a227dbdd
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Aug 20, 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.

3 participants