Answer stability round 2: 0 🔴, 1 🟡 (0 misread); put the dry-run note before the reason and warn in --help that another repo's chunk may take a place
CI / tests (pull_request) Failing after 3m38s
CI / tests (pull_request) Failing after 3m38s
This commit is contained in:
+2
-2
@@ -63,7 +63,7 @@ name says `awaits a slot`. In a repo whose config sets `merge = "human"`, a chun
|
||||
request is ready, with nothing else to wait on, the window's name says `awaits your merge`, and its worker goes on once you merged it. A parked chunk survives a reboot: run do-epic <EPIC-KEY> again to go on polling.
|
||||
--status doesn't start any chunk. It prints a line per open issue: that its chunk runs or asks you a question, or why it waits, such as the gate a parked chunk awaits and since when.
|
||||
--dry-run runs the planning and the scheduling against the epic as Jira holds it. It doesn't write anything to Jira, start a window or ask a question. It prints each label, sub-task, comment and rank move that planning would write, each chunk that would start and why each other issue waits. A sub-task not yet filed shows a key such as ABC-new1. A question planning would ask is printed instead of asked. Planning's claude calls still run.
|
||||
A repo that is missing isn't cloned. Planning then stops there, so its writes are only those made before it, and the issues of that repo wait; a real run would clone it and go on.
|
||||
A repo that is missing isn't cloned. Planning then stops there, so its writes are only those made before it, and the issues of that repo wait, and a chunk of another repo may start in the place a real run gives them; a real run would clone it and go on.
|
||||
{findings.HELP}
|
||||
{finish.HELP}
|
||||
The Jira site and its credentials are set in ~/.claude-projects/do-epic/config.toml."""
|
||||
@@ -189,7 +189,7 @@ def planned_and_started(epic: EpicRun, dry: bool = False) -> scheduler.Started |
|
||||
return Stop(1, f"the epic is not planned, so no chunk started: {stopped.said}")
|
||||
if stopped is not None:
|
||||
# One issue or repo that cannot be planned holds back only itself: each chunk that may start still does.
|
||||
say(f"the epic {epic.key} is not planned in full: {stopped.reason}" + (", so the writes below are those it made before it stopped" if dry else ""), epic.effects, stdout=dry)
|
||||
say(f"the epic {epic.key} is not planned in full" + (", so the writes below are those it made before it stopped" if dry else "") + f": {stopped.reason}", epic.effects, stdout=dry)
|
||||
started = chunks_started(epic, issues, None)
|
||||
return Stop(1, started.reason) if isinstance(started, Failure) else started
|
||||
|
||||
|
||||
@@ -1047,7 +1047,7 @@ class TheDryRun(DoEpicTest):
|
||||
fake = FakeEffects(on_terminal=False, git=["git@host.example:team/api.git", ""])
|
||||
code, out, err = self.run_main(["ABC-12", "--dry-run"], fake)
|
||||
self.assertEqual((code, err), (0, ""))
|
||||
stopped = f"the epic ABC-12 is not planned in full: cannot clone git@host.example:team/web to {self.home / 'code/web'}: a dry run doesn't clone a repo, but a real run would. Where does web live?, so the writes below are those it made before it stopped\n"
|
||||
stopped = f"the epic ABC-12 is not planned in full, so the writes below are those it made before it stopped: cannot clone git@host.example:team/web to {self.home / 'code/web'}: a dry run doesn't clone a repo, but a real run would. Where does web live?\n"
|
||||
self.assertIn(stopped, out.replace("<1790000000> ", ""))
|
||||
self.assertIn("planning wouldn't write anything to Jira\n", out)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user