Skip to content

armgit / rea

Public Imported from GitHub
0

Reverse engineer anything with agents, from app behavior down to native binaries.

ci: bound core job execution time

morluto9f3f392eb8fe
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 800574bde..b1af43269 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -34,6 +34,7 @@ jobs:
changes:
name: Classify changes
runs-on: ubuntu-latest
+ timeout-minutes: 5
permissions:
contents: read
actions: read
@@ -110,6 +111,7 @@ jobs:
needs: changes
if: ${{ !cancelled() && needs.changes.outputs.tier != 'reused' }}
runs-on: ubuntu-latest
+ timeout-minutes: 10
steps:
- name: Require successful change classification
env:
@@ -148,6 +150,7 @@ jobs:
needs: [changes, build]
if: needs.changes.outputs.code == 'true'
runs-on: ubuntu-latest
+ timeout-minutes: 30
strategy:
fail-fast: false
matrix:
@@ -188,6 +191,7 @@ jobs:
needs: changes
if: needs.changes.outputs.code == 'true'
runs-on: ubuntu-latest
+ timeout-minutes: 10
permissions:
contents: read
actions: read
@@ -258,6 +262,7 @@ jobs:
needs: [changes, test-shard]
if: ${{ !cancelled() && needs.changes.outputs.tier != 'reused' }}
runs-on: ubuntu-latest
+ timeout-minutes: 10
steps:
- name: Require successful change classification
env:
@@ -642,6 +647,7 @@ jobs:
needs: changes
if: needs.changes.outputs.docs == 'true'
runs-on: ubuntu-latest
+ timeout-minutes: 10
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
diff --git a/docs/testing.md b/docs/testing.md
index 5cd561b2b..22b5c0c77 100644
--- a/docs/testing.md
+++ b/docs/testing.md
@@ -292,6 +292,12 @@ coverage. This ordering reduces peak demand on invalid revisions but can add
static-check waiting to otherwise passing runs; it is not a measured reduction
in end-to-end latency.
+Core jobs have execution limits of five minutes for classification, ten minutes
+for static checks, builds, docs, and report merging, and thirty minutes per
+portable test shard. These limits leave headroom for cold setup and full coverage
+while preventing a hung job from holding the active main run for hours. They do
+not bound runner queue waiting. Timeouts still fail the required gate.
+
The separate `CI timings` workflow batches recent completed CI and Release runs
hourly or on manual dispatch. It uploads `ci-job-timings-batch` with raw API pages and
a normalized point-in-time report for each collected workflow attempt, plus a