The Windows log for #122 showed the mod stopping in the UI event (fuel budget 1e9, remaining 0) with known_units <- order_raid <- launch_wave <- ui_select: order_raid recomputed the planner snapshot known_units() for every drone, and the snapshot itself rescanned the whole force and the dedup list per intel entry. A second big Smart order cost drones x intel-log x force-size inside one event. Reproduced in actual WASM with measured per-callback fuel through the exact ui_select(BTN_LAUNCH) handler (diagnostic guest, trigger.patch): before, a 111-drone second order at revealed=13172/known=144 exhausted exactly 1e9 and stopped the mod (an 11-drone order at the same state: 247805865); after, the same scenario passes with max command fuel 32946177/1e9, failures=0, and /stats at tick 2602 byte-identical. A stacked single-point layout dies to one warhead (known=0, cheap order), so the scenario deploys spread clusters with a moved player. Fix: one known_units snapshot per order_raid passed to radar_strikes and choose_target; known_units is a single O(log + force) set pass; price_grid_on reuses its snapshot. Emitter/network targeting and carrier choice semantics are unchanged (native equivalence test against the former predicate; WASM checkpoint counters equal). Limits unchanged; HD/recording untouched; wave size unrestricted. Committed regressions: native snapshot-equivalence and second-smart-order tests; the heavy WASM fixture now orders two Smart raids through the wave screen's launch function (airdef preset + airdef raid) with EW and a combat intel log, four accepted orders asserted; the light contract covers preset and the empty-wave refusal. Core release 195 + 8 scenarios; adapter 65 + 1 boundary + 5 scenarios; light WASM 30 steps; heavy WASM 283 steps (tick max 182413686/300M, command max 6939810/1e9, failures 0). Windows GUI acceptance remains external and is not claimed. Co-Authored-By: Kimi Code (Moonshot AI) <noreply@moonshot.cn>
This commit is contained in:
+4
-2
@@ -158,7 +158,7 @@ def test_wasm():
|
||||
|
||||
|
||||
BUDGET_SCENARIO = "tests/budgets/wasm_flat_budget.toml"
|
||||
BUDGET_ASSERTED_SHA256 = "bcc0359289ab20ab3de608bcc130f72d2cf88f9f6fbc470d7b6846e9db5d11df"
|
||||
BUDGET_ASSERTED_SHA256 = "134cb4667691cf9faa639ed37120941d829cfc13ce45e9638582c409d9e0dd29"
|
||||
|
||||
|
||||
def fuel_measurements(output):
|
||||
@@ -280,8 +280,10 @@ def test_budgets():
|
||||
report["status"] = "failed"
|
||||
raise RuntimeError("pinned runtime did not return requested callback fuel counters")
|
||||
# These assertions belong to this exact fixture, not to arbitrary edited scripts.
|
||||
# Two `airdef wave oreshnik` orders plus two Smart orders through the UI launch
|
||||
# path (`airdef preset` + `airdef raid`, the wave screen's ПУСК handler, #122).
|
||||
if result.returncode == 0 and report["scenario_sha256"] == BUDGET_ASSERTED_SHA256:
|
||||
counts["accepted_raids_asserted"] = 2
|
||||
counts["accepted_raids_asserted"] = 4
|
||||
counts["snapshot_airborne_asserted"] = 184
|
||||
counts["snapshot_tick"] = 2102
|
||||
except Exception as exc:
|
||||
|
||||
@@ -123,7 +123,7 @@ class BudgetReportFailureTests(unittest.TestCase):
|
||||
self.assertEqual(report["scenario"], airdef.BUDGET_SCENARIO)
|
||||
self.assertEqual(report["scenario_render_world"], "flat at y=64")
|
||||
counts = report["scenario_counts"]
|
||||
self.assertEqual((counts["accepted_raids_asserted"], counts["snapshot_airborne_asserted"], counts["snapshot_tick"]), (2, 184, 2102))
|
||||
self.assertEqual((counts["accepted_raids_asserted"], counts["snapshot_airborne_asserted"], counts["snapshot_tick"]), (4, 184, 2102))
|
||||
self.assertIsNone(counts["peak_airborne_observed"])
|
||||
self.assertEqual(report["measured_fuel"]["callbacks"], [{
|
||||
"mod": "airdef", "callback": "tick", "calls": 2102,
|
||||
|
||||
Reference in New Issue
Block a user