create-objectstack#test failed in the 22:01Z schedule CI (job 120999879860) and passed live on push for the same commit 47af3dde42 — read the failing test from the job log and root-cause it #25715

Activity

1. objectstack-fleet

   added

   bugSomething isn't workingSomething isn't working

   priority:p2Medium: important, M3Medium: important, M3

   pm:queue

   area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterateThe road — create, dev, verify, publish/install, connect an agent, iterate

   domain:serverDomain lane — seat card indexed by label:pm:seatDomain lane — seat card indexed by label:pm:seat

   on Oct 24, 2026
2. objectstack-fleet commented on Oct 26, 2026

   

   objectstack-fleetBot

   on Oct 26, 2026

   ContributorAuthor

   More actions

   Ask to the maintainer · domain:server seat 1 · os-project-manager · session session_01R1q2xdtYgU6FKrZ7LgjPCC · 2026-10-26T09:08Z · ⛔ Not a claim.

   This card cannot be dispatched until someone reads the failing test. The seat's tools return only the tail of a job log, and the full download redirects to blob storage, which the cloud containers refuse.

   Wanted, pasted here as a comment: from CI schedule run 40136758584, job Test Core (4/6) (120999879860), step 15 "Run this shard's tests", the lines around create-objectstack:test: near log line 25155. That is the failing test's name and its error plus stack. One of these gets it:

   • gh run view 40136758584 --job 120999879860 --log | grep -n -A40 'create-objectstack:test:.*FAIL'
   • the web UI's log search for create-objectstack:test:

   Once that text is on the card, the seat dispatches it as written (root cause, ⛔ no skip, no retry wrapper).

   ---

   Generated by Claude Code
3. objectstack-fleet commented on Oct 27, 2026

   

   objectstack-fleetBot

   on Oct 27, 2026

   ContributorAuthor

   More actions

   Triage: pm:queue → pm:on-hold · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-27T01:56Z

   ⛔ Not a claim.

   • Why on hold: no seat can dispatch this card. The failing test's name sits about 8,600 lines before the end of a job log that our tools read only from the tail, and the full download is refused in the container. The ask to the maintainer to read the log (2026-10-26T09:08Z) has had no answer. Since then the schedule-CI reds were traced to other causes (the ui merge, the test(app-shell): re-point the ObjectSchema corpus guards to 48 after sharing was adopted #26231 corpus guards), and the last two schedule runs (2026-10-26T20:04Z, 2026-10-27T00:11Z) are green.
   • p2 and domain:server stand.

   Restart-when: create-objectstack fails again in any CI run (schedule, push or queue), or the maintainer pastes the failing test's name and error from job 120999879860.

   ---

   Generated by Claude Code
4. objectstack-fleet

   added

   pm:on-hold

   and removed

   pm:queue

   on Oct 27, 2026
5. objectstack-fleet commented on Oct 28, 2026

   

   objectstack-fleetBot

   on Oct 28, 2026

   ContributorAuthor

   More actions

   Occurrence · domain:server seat 2 · 2026-10-28T13:09Z

   The CI schedule run 40684983027 (12:05Z, head d745bb5e) is red again in Test Core (5/8) (job 122805706018). Its annotation reads: "command (…/packages/create-objectstack) pnpm run test exited (1)", at log line ≈33,634 of 42,113. That is outside the 5,000-line tail get_job_logs returns, so the failing test name was not read.

   Push CI on main at the same hours is green (for example 295699d5 and fbe344b3), so this is the schedule-only shape this card describes. The other schedule red, driver-sqlite-wasm (#27076), was fixed by PR #27245, so this card is now what stands between main and a green 4-hourly run. It stays pm:on-hold for the maintainer and triage; the seat dispatches nothing on it.

   ---

   Generated by Claude Code