Skip to content

54-ci: CI loose ends (perf-budget parts, script-guard, net-handshake) - #484

Merged
AlexZ005 merged 3 commits into
feat/54-intfrom
fix/54-ci
Nov 3, 2026
Merged

AlexZ005 merged 3 commits into
feat/54-intfrom
fix/54-ci

Conversation

@AlexZ005

@AlexZ005 AlexZ005 commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

Roadmap 54 rows X10 and X11 (X9 is in the cloud repo).

X10 — perf-budget under the job limit. perf-budget.yml always runs as a 3-part matrix (perf-budget 1/3..3/3, 50 min each), the split deps.yml already uses. Single-job runs took 53-73 min against the 75 min limit; one tag push in 1.45.0 timed out. No required check names this job.

X10 — e2e-smoke script-guard "a slow node is paused". Test-only fix. Since scripts run in the sandbox guest, the test's globalThis.__slowRuns counter was the guest's, so the page read 1. { timeout: 180000 } was passed as waitForFunction's arg, so the real limit was 30 s. The counter now rides the target box's position.z, the options are the third argument, and the runaway node is removed before the section.

X11 — net-handshake "C received the scene": the test waits for A to have received C's getobjects, then polls up to 90 s against A's current count (a red prints the C/A trail). The quarantine entry is removed.

Proof

  • First CI run on this PR: perf-budget 1/3 19.7 min, 2/3 16.9 min, 3/3 27.5 min (limit 50); e2e-smoke green, script-guard 11/11 in 124 s (red at 109 s on v1.44.0, run 40227427957).
  • GPU host A/B against v1.45.1: net-handshake fix 3/3 green; the trail shows C at 0/5 and 4/5 for up to 12 s before 5/5, the window the old fixed read raced. The old test was also 3/3 green there. script-guard at 6× CPU throttle: the suite took 63 s with the fix vs 116 s with the old test. Both variants fail "a while(true) node reports the loop limit" only under that throttle; that check is unchanged, and unthrottled it passes 11/11.

🤖 Generated with Claude Code

AlexZ005 and others added 3 commits October 27, 2026 04:52
- one job took 53-73 min against its 75 min limit; release.yml's run for
  1.45.0 timed out with three perf-budget runs started by one tag push
- the push / PR / release.yml triggers now run the --part 1/3..3/3 matrix
  deps.yml already used (~20-25 min a part); deps.yml's per-part calls are
  unchanged; per-part limit 50 min
- no required check names the job (only deps-gate / pc-battery on deps)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…80 s (54 X10)

Since the scripts moved into the sandbox guest, globalThis.__slowRuns was the
guest's global, so the page always read 1; and { timeout: 180000 } sat in the
arg slot of waitForFunction, so the wait ended at the 30 s default. On a
~4 fps runner the 30 slow runs plus the runaway node's per-frame loop limit
take longer than that: red on CI since 1.44.0. The counter now rides the
target box's position.z, the options are the third argument, the runaway
node is removed before the section, and the label carries runs + seconds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… out of quarantine (54 X11)

The third peer's "C received the scene" read C's count after a fixed wait and
was red on CI and under load with C partway (1/3/4 of 5). It now waits for A
to have received C's getobjects (premise), then polls up to 90 s comparing C
with A's current count; a red carries the C/A trail over time. A's five boxes
are polled instead of a 1 s wait, and "C holds open conns" is bounded at 60 s.
On a GPU host the trail shows C at 0/5 and 4/5 for up to 12 s before 5/5
(3/3 green), the window a fixed read raced.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@AlexZ005
AlexZ005 marked this pull request as ready for review October 27, 2026 08:26
@AlexZ005
AlexZ005 merged commit ba0bbf6 into feat/54-int Nov 3, 2026
11 checks passed
@AlexZ005
AlexZ005 deleted the fix/54-ci branch November 3, 2026 00:39
@AlexZ005

AlexZ005 commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator Author

In main via 54-int: released as v1.54.3 (#522, 9c202d1).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant