nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
Nx
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
GitHub
Nx
Workspace
Succeeded
36986
450f46e9 cleanup(core): correct run-state comments and pin exit and recovery cases in migrate orchestrator specs The closed-set JSDoc on NewerRunStateFormatError demanded a format bump for every new member, but `unresolved` joined the step statuses at v1 on purpose: runs are not supported across Nx versions while the orchestrator is dark, and the bump waits for its promotion. The `adopted` field comment excluded a dead worker's landed commit, which adopt also accepts. Specs gain the `recorded` disposition in the master-session exit table and a died step with no cached broker answer, which keeps skip and unresolved open and records no entry.
by Leosvel Pé...
L
Failed
36986
Flaky task
→
450f46e9 cleanup(core): correct run-state comments and pin exit and recovery cases in migrate orchestrator specs The closed-set JSDoc on NewerRunStateFormatError demanded a format bump for every new member, but `unresolved` joined the step statuses at v1 on purpose: runs are not supported across Nx versions while the orchestrator is dark, and the bump waits for its promotion. The `adopted` field comment excluded a dead worker's landed commit, which adopt also accepts. Specs gain the `recorded` disposition in the master-session exit table and a died step with no cached broker answer, which keeps skip and unresolved open and records no entry.
by Leosvel Pé...
L
Failed
36986
Fix available
→
e75eeee1 cleanup(core): correct run-state comments and pin exit and recovery cases in migrate orchestrator specs The closed-set JSDoc on NewerRunStateFormatError demanded a format bump for every new member, but `unresolved` joined the step statuses at v1 on purpose: runs are not supported across Nx versions while the orchestrator is dark, and the bump waits for its promotion. The `adopted` field comment excluded a dead worker's landed commit, which adopt also accepts. Specs gain the `recorded` disposition in the master-session exit table and a died step with no cached broker answer, which keeps skip and unresolved open and records no entry.
by Leosvel Pé...
L
Canceled
36986
1778d909 fix(core): keep every recorded commit of an orchestrated migrate step out of skip and unresolved The gate that withholds and refuses skip and unresolved for a landed commit reused the reset-hazard check, which ignores an earlier attempt's commit once it is an ancestor of the re-captured ref and cannot see a commit the session landed for the current attempt when the worker died between the broker's answer and its ledger append. A retried step that failed again, or a worker killed in that window, could be recorded skipped or unresolved with its commit in history. The gate, both dispenses and the adopt request choice now use the last ledger entry covering the step, whichever attempt landed it. Reconcile recovers a dead worker's brokered commit from the session's cached answer before validating any step action, and appends it once: landed entries record the attempt that landed them (ownerAttempt), with the sha as the key for entries written before the field existed. A commit a worker made in-process and died before recording leaves no answer and is not detected; the runbook, the repo skill and the PR body say the options are withheld for a commit the run has on record.
by Leosvel Pé...
L
Failed
36986
9bc61402 fix(core): keep a landed commit when an orchestrated migrate step is adopted, skipped or given up A worker commits its migration before it reports the outcome, so a step can fail or die with its commit already in the ledger. Adopting such a died step re-published the worker's own commit request; under the session broker the cached answer came back and the ledger entry landed twice, and in-process the tree was committed again under the worker's name. The failed and died dispenses also offered skip and unresolved for the step, and acceptance took them, so the run could record a migration whose result sits in history as skipped or given up. Adopt now asks under its own commit-adopt request whenever the step is failed or its commit already landed, so a cached worker answer is never replayed and repairs made since land as their own commit. Skip and unresolved are withheld from both dispenses and refused at acceptance, naming the landed sha and pointing to adopt; the retry budget, cap and retry-clean fallback lines, the runbook and the multi-repo migrate skill say the same. The persisted failed-adopt summary no longer claims the tree was applied by hand. The overlong-id digest test gives both steps the same attempt and failure so only the digest tells the summaries apart; the broker seam comment is scoped to a failure with no landed entry.
by Leosvel Pé...
L
Failed
36986
Generating fix
→
9bc61402 fix(core): keep a landed commit when an orchestrated migrate step is adopted, skipped or given up A worker commits its migration before it reports the outcome, so a step can fail or die with its commit already in the ledger. Adopting such a died step re-published the worker's own commit request; under the session broker the cached answer came back and the ledger entry landed twice, and in-process the tree was committed again under the worker's name. The failed and died dispenses also offered skip and unresolved for the step, and acceptance took them, so the run could record a migration whose result sits in history as skipped or given up. Adopt now asks under its own commit-adopt request whenever the step is failed or its commit already landed, so a cached worker answer is never replayed and repairs made since land as their own commit. Skip and unresolved are withheld from both dispenses and refused at acceptance, naming the landed sha and pointing to adopt; the retry budget, cap and retry-clean fallback lines, the runbook and the multi-repo migrate skill say the same. The persisted failed-adopt summary no longer claims the tree was applied by hand. The overlong-id digest test gives both steps the same attempt and failure so only the digest tells the summaries apart; the broker seam comment is scoped to a failure with no landed entry.
by Leosvel Pé...
L
Succeeded
36986
2b72e48d cleanup(core): cover giving up, adopting, and the retry cap in the migrate orchestrator e2e Five orchestrator cases: give up on a killed worker by reset and check the minted issue, commit the partial tree of a given-up prompt step under its name marked unresolved, adopt a failed prompt step applied by hand, refuse a retry past two rearms, and a master session that exits 1 with the given-up migration in its report. The fake agent gives a step up through the dispense's unresolved option only when FAKE_AGENT_FAIL_PROMPTS makes its prompt-based migrations fail; generator validation handoffs still succeed and retry-failed still retries otherwise.
by Leosvel Pé...
L
Canceled
36986
5f76bda8 cleanup(core): cover giving up, adopting, and the retry cap in the migrate orchestrator e2e Five orchestrator cases: give up on a killed worker by reset and check the minted issue, commit the partial tree of a given-up prompt step under its name marked unresolved, adopt a failed prompt step applied by hand, refuse a retry past two rearms, and a master session that exits 1 with the given-up migration in its report. The fake agent gives a step up through the dispense's unresolved option only when FAKE_AGENT_FAIL_PROMPTS makes its prompt-based migrations fail; generator validation handoffs still succeed and retry-failed still retries otherwise.
by Leosvel Pé...
L
Failed
36986
Flaky task
→
5f76bda8 cleanup(core): cover giving up, adopting, and the retry cap in the migrate orchestrator e2e Five orchestrator cases: give up on a killed worker by reset and check the minted issue, commit the partial tree of a given-up prompt step under its name marked unresolved, adopt a failed prompt step applied by hand, refuse a retry past two rearms, and a master session that exits 1 with the given-up migration in its report. The fake agent gives a step up through the dispense's unresolved option only when FAKE_AGENT_FAIL_PROMPTS makes its prompt-based migrations fail; generator validation handoffs still succeed and retry-failed still retries otherwise.
by Leosvel Pé...
L
Previous
Next