CI: initial fuzzer jobs

[ordian]

See https://github.com/paritytech/ci_cd/issues/64.

The initial version doesn't have automatic notification on failure, but that could be added later. I've spent too much on it already.

[lovelaced]

This looks fine to me, though if you want to go ahead and add a matrix message step it would look something like:

 - steps:
  ...
  - name: bash script step
  ...
  - name: Fuzzer found something
    if: ${{ failure() }}
     uses: s3krit/matrix-message-action@v0.0.3
     with:
         room_id: ${{ secrets.MATRIX_ROOM_ID_FUZZER }}
         access_token: ${{ secrets.MATRIX_ACCESS_TOKEN_FUZZER }}
         message: "uh oh... ${{ github.event.workflow_run.url }}"
         server: "matrix.parity.io"

[ordian]

Saw something that shouldn't act like this.

Thanks, fixed in 86333c5.

Also, the default timeout is 360 min.

This is 6 hours, we run fuzzers for 5 hours, 1 extra hour should be enough for builds.

[TriplEight]

I meant, in general. Are we good running fuzzing on rather weak public github hosts?

[ordian]

I meant, in general. Are we good running fuzzing on rather weak public github hosts?

Well, we want something working now. So I'd say it's good as is for now until we have more CI dev-time to borrow.

[TriplEight]

Everything looks good. Maybe give them a debug run before the merge?

[TriplEight]

👍