Establish a complete-suite result for BuildTest resource estimate reuse
Written 2026-10-27 04:08 UTC.
RE-VERIFY: This is a write-time snapshot. Check the source branches, captured XML root flags, and actual run state before continuing.
Required behavior
The owner requires: "Never merge, enqueue, deploy or publish." The brief permits one complete-suite race for this lane and prohibits raising timeouts or limits, reducing iterations, or changing production state. That race has already been attempted; ask the orchestrator before another complete attempt.
Mission
Resolve the remaining full-suite verification gate for the incremental BuildTest dispatch projection without changing the existing limits or test work counts.
Observed state
The remote complete run 55466e9e returned exit 1 during provisioning. Its fleet lookup reported UNKNOWN_METHOD and no registered digitalocean-droplets service. Its XML has remote-failed=true and 5349 synthetic unsuccessful rows at time zero; these are not executed tests.
The local complete command returned exit 137 after about 53 minutes, without XML. The initiating cause is unknown. A shared cgroup memory ceiling of 10 GiB and cumulative memory termination counters were observed, without a before-sample tying them to this command. No actual Java heap error trace was found in the local log. Do not treat those cumulative counters as a demonstrated cause.
The targeted regression passes on its first attempt in two independent commands. The original implementation and reversal control each report five global calculations instead of one on all three attempts. This blocker concerns complete-suite evidence, not an observed defect in the targeted implementation.
References
Next steps
- Establish the reason for local exit 137 from the captured records and execution environment, without increasing the shared ceiling.
- Read the droplet-service lookup state through its owning component; no production changes are authorized here.
- Ask the orchestrator how to obtain another complete-suite result after the one permitted race ended without usable results. Do not submit another automatically.
No code was deployed, no service was restarted, and no Maven artifact was published by this lane.