mirror of
https://github.com/zvx-echo6/meshai.git
synced 2026-08-26 17:31:34 +00:00
Triaged all 20 known-red tests. 13 were stale tests asserting rotted expectations against deliberate, documented behavior changes; fixed by deriving expected values instead of hard-coding, or updating the expectation to match a documented policy change: - test_adapter_config_foundation.py / test_adapter_config_api.py: REGISTRY/API key-count and key-set guards hard-coded magic numbers (59/94/17) that rotted repeatedly. Now derive expectations from REGISTRY itself and, for the schema version, from the migrations directory, so they can't rot the same way again. - test_fire_tracker_phase4.py: two tests hardcoded a nonexistent deployment path (/opt/meshai/meshai/router.py) that matches no Dockerfile WORKDIR in this repo; resolve the module path via importlib.util.find_spec instead. - test_tombstone_broadcast.py: asserted fire severity == "immediate", which commit2f677e85deliberately downgraded to "priority" (to stop fire broadcasts bypassing the Grouper/cooldown during NATS backlog replay) without updating this test. - test_pipeline_grouper.py: test_immediate_severity_bypasses_grouper asserted an immediate-severity bypass that commit85d48ce3("fix(fire): remove immediate-severity exemption from grouper + cooldown") DELETED on purpose -- fire events carry _severity_override="immediate", and the exemption left fire with no rate control at all in normal live operation. Re-adding the bypass would re-open that fire-spam hole on a public-safety mesh, so the test moves, not the source. Renamed + inverted to assert the real contract (all severities coalesce; only a missing group_key passes through). - test_tail_followups.py: dispatcher mock was missing dispatch_scheduled_fire_broadcast (a method added alongside the generic dispatch_scheduled_broadcast; test_reminders.py already mocks both). - test_tracking_v057.py: guard required an empty tracking-family adapter list in Environment.tsx, but the frontend has long grouped the pre-existing native satpass adapter under the "Tracking" display section (its own "satpass" backend toggle, unrelated to the Phase-7 tracking family every other guard in this file confirms is still unimplemented). Narrowed the guard to allow only that known entry. - test_v052_dispatcher.py: two tests used category="wildfire_incident", which the phase3b fire migration (#33) forced onto a dedicated formatter via NATIVE_ALWAYS_DECIDE; swapped to wildfire_hotspot (same emoji/label, not in NATIVE_ALWAYS_DECIDE) to keep exercising the generic composer logic under test. Also fixes one stale COMMENT (comment-only, no logic change) in meshai/notifications/pipeline/__init__.py's start_pipeline(): it still claimed "Immediate events bypass the grouper and don't need this [periodic flush]", which has been false since85d48ce3and is precisely what makes the deleted bypass look like a missing feature. The comment now records that the removal was deliberate and must not be reverted. The remaining 6 failures are left untouched -- 2 confirmed real bugs, to be fixed deliberately in their own changes: - meshcore_transport.py defines `_resolve_contact` TWICE on MeshCoreTransport (line 171 from PR #56, line 1227 from PR #92). The second silently shadows the first, so the DM contact-resolution refetch-on-miss that #56 added is dead code in production. (3 tests) - SCHEMA_VERSION (persistence/db.py:33) is stale at 26 vs. the actual highest migration v28; v27 and v28 shipped without bumping it. (3 tests) Plus 1 environment gap, not a code defect: test_natural_language_fire_question_routes_to_llm needs the `openai` package, which is declared in requirements.txt but not installed here. Suite: 20 failed, 2240 passed, 72 skipped -> 7 failed, 2254 passed, 72 skipped. All 7 remaining failures are ones classified above; no new failures introduced elsewhere in the suite. Co-authored-by: Matt Johnson <mj@k7zvx.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
96 lines
3.5 KiB
Python
96 lines
3.5 KiB
Python
"""Grouper tests: coalescing (all severities) + periodic flush.
|
|
|
|
Note: there is deliberately NO immediate-severity bypass -- commit 85d48ce3
|
|
removed it so fire broadcasts obey rate control. The only pass-through is
|
|
"event has no group_key".
|
|
"""
|
|
|
|
from meshai.notifications.pipeline.grouper import Grouper
|
|
from meshai.notifications.events import make_event
|
|
|
|
|
|
class Recorder:
|
|
def __init__(self):
|
|
self.received = []
|
|
|
|
def handle(self, event):
|
|
self.received.append(event)
|
|
|
|
|
|
def _ev(severity, group_key="gk1"):
|
|
return make_event(
|
|
source="usgs_quake",
|
|
category="earthquake_event",
|
|
severity=severity,
|
|
title=f"test {severity}",
|
|
lat=42.6,
|
|
lon=-114.5,
|
|
group_key=group_key,
|
|
inhibit_keys=[group_key],
|
|
)
|
|
|
|
|
|
def test_immediate_severity_is_also_coalesced_no_bypass():
|
|
"""An immediate event WITH a group_key is held, like every other severity.
|
|
|
|
The grouper used to exempt severity == "immediate" from the coalescing
|
|
window. Commit 85d48ce3 ("fix(fire): remove immediate-severity exemption
|
|
from grouper + cooldown") DELETED that bypass on purpose: fire events
|
|
carry _severity_override="immediate", and the exemption meant they
|
|
skipped the coalescer and zeroed the dispatcher cooldown, leaving fire
|
|
with no rate control at all in normal live operation. Rate control now
|
|
applies to ALL severities; the drain-mode pacer covers reconnect bursts.
|
|
|
|
This test previously asserted the OLD bypass contract and had been red
|
|
ever since. Re-adding the bypass to make it pass would re-open the fire
|
|
broadcast-spam hole on a public-safety mesh -- so the test is what moves,
|
|
not the source.
|
|
"""
|
|
rec = Recorder()
|
|
g = Grouper(next_handler=rec.handle, window_seconds=60.0)
|
|
g.handle(_ev("immediate"))
|
|
# Held for coalescing, NOT delivered straight through.
|
|
assert rec.received == []
|
|
assert g.held_count() == 1
|
|
# The periodic flush (start_pipeline's _grouper_flush_loop) is what
|
|
# eventually delivers it, once the window expires.
|
|
g2 = Grouper(next_handler=rec.handle, window_seconds=0.0)
|
|
g2.handle(_ev("immediate", group_key="gk2"))
|
|
assert g2.tick() == 1
|
|
assert len(rec.received) == 1
|
|
assert rec.received[0].severity == "immediate"
|
|
|
|
|
|
def test_no_group_key_still_passes_through_immediately():
|
|
"""The ONE remaining bypass: an event with no group_key isn't coalesced
|
|
(there's nothing to coalesce it against)."""
|
|
rec = Recorder()
|
|
g = Grouper(next_handler=rec.handle, window_seconds=60.0)
|
|
g.handle(_ev("immediate", group_key=None))
|
|
assert len(rec.received) == 1
|
|
assert g.held_count() == 0
|
|
|
|
|
|
def test_periodic_flush_drains_routine():
|
|
"""A routine event is held, then released by tick() once its window passes."""
|
|
rec = Recorder()
|
|
g = Grouper(next_handler=rec.handle, window_seconds=0.0) # 0s window -> tick drains now
|
|
g.handle(_ev("routine"))
|
|
# Held on arrival, not yet delivered.
|
|
assert g.held_count() == 1
|
|
assert rec.received == []
|
|
# The periodic flush task calls tick(); simulate one tick.
|
|
drained = g.tick()
|
|
assert drained == 1
|
|
assert len(rec.received) == 1
|
|
assert rec.received[0].severity == "routine"
|
|
assert g.held_count() == 0
|
|
|
|
|
|
def test_priority_is_also_coalesced_not_bypassed():
|
|
"""Priority events still buffer (only immediate bypasses)."""
|
|
rec = Recorder()
|
|
g = Grouper(next_handler=rec.handle, window_seconds=60.0)
|
|
g.handle(_ev("priority"))
|
|
assert rec.received == []
|
|
assert g.held_count() == 1
|