> My PR build just went red on testDropSession. Diagnose only: is this failure related to my change? https://develocity.example.com/s/k7d2q9xmfa3p4
Phase 1 / 5: Resolve Scan — the Build Scan came with the ask, no ID to hunt for
Phase 2 / 5: Triage — checking the failure against builds beyond yours, last seven days
develocity — get_build (MCP)(buildId: k7d2q9xmfa3p4, models: tests)subject: SessionReconnectIntegrationTest.testDropSession() — 689 passed, 6 failed, 0 flaky
develocity — list_failure_groups (MCP)(project: payments-service, window: 7d)matched group: 1446 occurrences across 12 builds, every one on feature/session-pool
independent recurrence 9tq4wz2mh8c1e — different commit, CI run and host, before your change existed
Phase 3 / 5: Diagnose —
Read(core/…/session/SessionRegistry.java)Read 48 lines — listener empty at init, set(null) on 3 paths, read unguarded at :1061 and :1086
Phase 4 / 5: Respond —
Root cause analysis
VerdictPRE-EXISTINGnot caused by your change — the same signature fails in 12 builds that do not contain it
ClassificationCODE-FIXABLELOCALone branch, one project, CI only
Root causeSessionRegistry.listener may hold null; every reconnect entry point reads it unguarded
Evidencek7d2q9xmfa3p4 · 9tq4wz2mh8c1e · failure group on feature/session-pool
Reproduction./gradlew :core:test --tests SessionRegistryTest at the failing commit
Diagnose only, so I stop here and change nothing. Carry on with your task — say handle it and I open the pull request.