rust-bitcoin / rust-bitcoin / 8456283848 / 1

83%

master: 83%

push

github

Merge rust-bitcoin/rust-bitcoin#2634: Run fuzzer daily

<a class=hub.com/rust-bitcoin/rust-bitcoin/commit/6ab0110964af9f8b39b52346e0c49dcad468c797">6ab011096 Run fuzzer daily (Tobin C. Harding)

Pull request description:

  Waiting for the fuzzer slows down the dev feedback loop because it makes CI slow. We still want fuzz coverage but not in a way that slows down devs.

  Instead of running the fuzzer on every PR just run it once a nightly.

  As we do for other daily jobs, rename the yaml file to make explicit what it does.

  Note also we only get 20 jobs, currently there are 18 fuzzing jobs. This means for this hour any other CI runs will only have access to 2 jobs (if i understand GitHub resource usage correctly).

  ### Open questions

  Docs: https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration

  > Concurrent jobs - The number of concurrent jobs you can run in your account depends on your GitHub plan,

  What is the definition of "account" - is that a user account, or a repository? Which account is running the cron job?

ACKs for top commit:
  apoelstra:
    ACK 6ab0110964af9f8b39b52346e0c49dcad468c797 though if this proves too onerous we should try 30 or even 15 minutes

Tree-SHA512: d6d07d16b788da3cf03cd4cd542d4112d4e

19066 of 22909 relevant lines covered (83.22%)

16860.02 hits per line