Skip to content

ci: the actor simulation runs every night on queen, dispatched from main (Closes #1873) - #1874

Merged
gHashTag merged 1 commit into
mainfrom
queen-sim-nightly
Oct 17, 2026
Merged

gHashTag merged 1 commit into
mainfrom
queen-sim-nightly

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #1873

Part of #1868 (plan #1763, ledger #1729): the actor simulation gate runs every night on queen.

Why a file on main

GitHub runs a schedule only from the default branch, which is main here. A cron in queen's .github/workflows/queen-actors-sim.yml would never fire.

What

.github/workflows/queen-sim-nightly.yml runs on a schedule (02:17 UTC) and on workflow_dispatch. It runs:

gh workflow run queen-actors-sim.yml --ref queen -f nightly=true -f recreate=none

It needs only actions: write; the GITHUB_TOKEN may dispatch, and a workflow_dispatch it sends starts a run. Everything else lives on queen, beside the code it tests: the gate, its job, and the step that, on a failed nightly run, comments on (or opens) the issue labelled sim-nightly with the seed and the first broken invariant.

The dispatch path was checked by hand: gh workflow run queen-actors-sim.yml --ref sim-keyed-pool started run 38129493949, though the workflow file is not on main.

Merge order

Merge this after the queen PR of #1868. That PR adds the workflow_dispatch inputs (nightly, recreate) this dispatch passes. Until then, the dispatch is refused.

🤖 Generated with Claude Code

…ain (Closes #1873)

GitHub runs a schedule only from the default branch, main. This workflow
dispatches queen-actors-sim.yml on queen with nightly=true every night at
02:17 UTC; a failed night comments on or opens the sim-nightly issue from
that run. Part of #1868.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tri-claw

tri-claw Bot commented Oct 11, 2026

Copy link
Copy Markdown

Summary by t27-bees

This PR adds a nightly scheduled workflow on main that dispatches the actor simulation workflow on the queen branch. Since GitHub only executes schedule triggers from the default branch (main), this wrapper workflow runs at 02:17 UTC and uses gh workflow run to start queen-actors-sim.yml on queen with nightly=true and recreate=none.

Worth a look

  • .github/workflows/queen-sim-nightly.yml:30 — The dispatch will fail if the queen branch lacks queen-actors-sim.yml with the expected workflow_dispatch inputs (nightly, recreate). The PR description notes this must be merged after the queen PR that adds those inputs; merging out of order breaks the nightly run silently (the dispatch is refused).
  • .github/workflows/queen-sim-nightly.yml:23 — concurrency.cancel-in-progress: false means a manual workflow_dispatch during a scheduled run queues a second dispatch. Both will execute, potentially doubling the simulation load on queen.
  • .github/workflows/queen-sim-nightly.yml:33 — The gh CLI command assumes queen-actors-sim.yml exists at the root of .github/workflows/ on the queen branch. If that workflow lives in a subdirectory or is renamed, the dispatch fails with a confusing error.

Read: 1 files, +41 -0, the whole diff. Head 9cb029d. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

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.

Nightly actor simulation on queen: a schedule trampoline on main

1 participant