Weekly medic benchmark #32
lzgabelmedic-benchmarks.yml
on: schedule
Latency Benchmark
/
Build Starter and Worker
Latency Benchmark
/
Build Zeebe
Mixed Benchmark
/
Build Starter and Worker
Mixed Benchmark
/
Build Zeebe
Normal Benchmark
/
Build Starter and Worker
Normal Benchmark
/
Build Zeebe
Latency Benchmark
/
Deploy
Mixed Benchmark
/
Deploy
Normal Benchmark
/
Deploy
Latency Benchmark
/
...
/
cleanup
Latency Benchmark
/
...
/
publish-to-pull-request
Latency Benchmark
/
...
/
publish-to-slack
Mixed Benchmark
/
...
/
cleanup
Mixed Benchmark
/
...
/
publish-to-pull-request
Mixed Benchmark
/
...
/
publish-to-slack
Normal Benchmark
/
...
/
cleanup
Normal Benchmark
/
...
/
publish-to-pull-request
Normal Benchmark
/
...
/
publish-to-slack
Annotations
1 error
|
Invalid workflow file:
.github/workflows/medic-benchmarks.yml#L160
The workflow is not valid. lzgabel/zeebe/.github/workflows/benchmark.yml@bab683c7677b63113dfa4833338179c9c90295a4 (Line: 160, Col: 3): Error calling workflow 'zeebe-io/zeebe-performance-test/.github/workflows/measure.yaml@main'. The nested job 'setup' is requesting 'id-token: write', but is only allowed 'id-token: none'. lzgabel/zeebe/.github/workflows/benchmark.yml@bab683c7677b63113dfa4833338179c9c90295a4 (Line: 160, Col: 3): Error calling workflow 'zeebe-io/zeebe-performance-test/.github/workflows/measure.yaml@main'. The nested job 'measure-before' is requesting 'id-token: write', but is only allowed 'id-token: none'.
|