Relationships
#4030 Flaky: worker_enroll_phase_telemetry_test asserts the order of a lookup's definition_scan spans
Opened by skunk-ape · 10/27/2026· Shipped 10/27/2026
integration/worker_enroll_phase_telemetry_test.ts ("enrollment phases: new and existing workers export their lookups, lock, save and adoption through OTLP") failed once in verify-build at 2026-10-27 17:37 UTC (run db525353-086f-4742-8cb1-646ed540055d, branch for swamp-club#3972, which does not touch worker enrollment or tracing). It passed 3/3 when re-run alone.
The assertion near line 447 maps each lookup child scan to [scan_strategy, lookup_attempt] and compares the list in a fixed order. Actual was [["name_index","recheck"],["full_listing","recheck"]], expected [["full_listing","recheck"],["name_index","recheck"]]: same spans, other order. The spans are filtered from the exported batch, whose order is not guaranteed under parallel load.
Fix: sort the scans (by strategy) before comparing, or compare as a set. Introduced with the worker-enrollment phase spans (swamp-club#3986).
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.