FrankChen021 commented on PR #20285:
URL: https://github.com/apache/druid/pull/20285#issuecomment-5583889830

   MergeLens evidence for exact head 3f22201272941fdb3332fb2dfd89cac0389cd787
   
   - Live PR head is unchanged. GitHub PR base/merge ref remain 
9b90983fd291f26935af934383ce360473179e4d / 
e709f823921cfd858955fdbe573127f6f62c9504. Isolated fetch shows remote master 
advanced to 33f7f778dfc2d8b06ca7c1d7a93f54f162526cee via ci: Fix 
SupervisorManagerTest (#20294).
   - Exact-head CI: 27 completed SUCCESS contexts, including the previously 
retried K* unit shard and the permitted Docker rerun. One actions-timeline 
context is still QUEUED with no runner or steps; it is informational, and no 
required checks are reported for this branch.
   - Prior attempt evidence: attempt 1 had KubernetesTaskRunnerTest assertion 
failures and a KafkaBoundedSupervisorTest timeout; attempt 2 had an 
IngestionDockerTest timeout. Attempt 3 passed those retried gates. None was 
caused by the Byte Buddy version bump, and no deterministic moving-base compile 
failure remains.
   - Compatibility audit for the only published transition 1.18.12 to 1.18.13: 
API/ABI SAFE; runtime SAFE; configuration SAFE; serialization/wire SAFE; 
persistence SAFE; clients/transports SAFE; transitive dependencies SAFE; 
licenses SAFE; extension/plugin SPI SAFE. The PR only changes the root pom.xml 
dependency-management property from 1.18.12 to 1.18.13; no source or test 
changes are needed.
   
   I will approve after the exact-head review state is recorded; this comment 
is the pre-approval evidence record.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to