Portability CI: the timeout comment names the runner cap that still binds
All checks were successful
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 23m17s
All checks were successful
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 23m17s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
44f54b8015
commit
3b1c39fd76
1 changed files with 2 additions and 1 deletions
3
.github/workflows/cultmesh-portability.yml
vendored
3
.github/workflows/cultmesh-portability.yml
vendored
|
|
@ -25,7 +25,8 @@ jobs:
|
|||
reactive-and-resource-lifetime:
|
||||
name: ${{ matrix.os }} reactive semantics and leases
|
||||
runs-on: ${{ matrix.os }}
|
||||
# The forge runner cap is 60 minutes; the job value must match or the job dies at the lower of the two.
|
||||
# The job dies at the lower of this value and the forge runner's own cap, which Eureka is raising from 30 to 60 minutes
|
||||
# (run 1378 carried 60 and was still cancelled at 30:02); the two must both say 60 before a full run can finish.
|
||||
timeout-minutes: 60
|
||||
strategy:
|
||||
fail-fast: false
|
||||
|
|
|
|||
Loading…
Reference in a new issue