You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let the backends own their teardown budget and no-input story
Each backend now publishes the teardown budget its own constants add up to and
the CLI waits out the longest one reachable on this platform, so a ConPTY
teardown is no longer reported as a render that did not stop. The absent-input
note comes from the backend that ran rather than from sys.platform, which was
wrong under the escape hatch on Windows. The POSIX grace probes the process
group each tick and ends early once it is spent, and the precondition check asks
each repository once for the whole list of previous frids.
f"Cannot start rendering from functionality {first_render_frid} for module '{self.module_name}' because the implementation of the previous functionality ({frid}) hasn't been completed yet.\n\n"
307
-
f"To fix this, please render the missing functionality ({frid}) first by running:\n"
f"Cannot start rendering from functionality {first_render_frid} for module '{self.module_name}' because the implementation of the previous functionality ({frid}) hasn't been completed yet.\n\n"
319
+
f"To fix this, please render the missing functionality ({frid}) first by running:\n"
f"Cannot start rendering from functionality {first_render_frid} for module '{self.module_name}' because the conformance tests for the previous functionality ({frid}) haven't been completed yet.\n\n"
316
326
f"To fix this, please render the missing functionality ({frid}) first by running:\n"
0 commit comments