This issue was generated automatically by Claude Code (Anthropic's AI coding agent) running a scheduled CI-triage routine on behalf of @FrankChen021. Analysis and suggested fixes are AI-produced; please verify before acting on them.
Status: Resolved by #20552
Subject: QueryVirtualStorageTest.testQueryTooMuchData (embedded-tests, unit tests (25, N*,Q*))
Failures: 2 · First seen: 2026-10-08 · Last seen: 2026-10-10
Root cause
The query fails as intended, but the assertion at QueryVirtualStorageTest.java:166 requires the exact message Unable to reserve bundle. With a 1 MiB cache and virtualStorageLoadThreads set to the CPU count, which reservation runs out of space first depends on thread timing. PartialSegmentMetadataCacheEntry throws Unable to reserve bundle[...], SegmentLocalCacheManager.reservePartial throws Unable to reserve partial metadata for segment[...], and the full-load path throws Unable to load segment[...] on demand. All three are CAPACITY_EXCEEDED, but only the first one passes the test. The failing commit (#20508) changes only Dart worker discovery, and the job passed on the neighbouring master commits.
Suggested fix
Assert on what all three capacity errors share: the CAPACITY_EXCEEDED category, or the substring ensure enough disk space has been allocated. Don't match the bundle-specific message, and include t.getMessage() in the assertion message so a future mismatch shows the actual error.
Merged fix: #20552 (2026-10-11).
Occurrences
Failed push-triggered master jobs only. The daily triage routine adds one row per new failed job.
| Date |
Commit |
Job |
Failure log |
Detail |
Reported in |
| 2026-10-08 |
3cedc8a (#20508) |
unit tests / unit tests(main) (25, N*,Q*) / test-jdk25-[N*,Q*] |
job 113564498218 |
expected: <true> but was: <false> at line 166 (message lacked Unable to reserve bundle); single attempt, no surefire retry |
|
| 2026-10-10 |
66504db (#20532) |
unit tests / unit tests(main) (25, N*,Q*) / test-jdk25-[N*,Q*] |
job 114106294400 |
expected: <true> but was: <false> at line 166; single attempt, no surefire retry |
|
This issue was generated automatically by Claude Code (Anthropic's AI coding agent) running a scheduled CI-triage routine on behalf of @FrankChen021. Analysis and suggested fixes are AI-produced; please verify before acting on them.
Status: Resolved by #20552
Subject:
QueryVirtualStorageTest.testQueryTooMuchData(embedded-tests,unit tests (25, N*,Q*))Failures: 2 · First seen: 2026-10-08 · Last seen: 2026-10-10
Root cause
The query fails as intended, but the assertion at
QueryVirtualStorageTest.java:166requires the exact messageUnable to reserve bundle. With a 1 MiB cache andvirtualStorageLoadThreadsset to the CPU count, which reservation runs out of space first depends on thread timing.PartialSegmentMetadataCacheEntrythrowsUnable to reserve bundle[...],SegmentLocalCacheManager.reservePartialthrowsUnable to reserve partial metadata for segment[...], and the full-load path throwsUnable to load segment[...] on demand. All three areCAPACITY_EXCEEDED, but only the first one passes the test. The failing commit (#20508) changes only Dart worker discovery, and the job passed on the neighbouring master commits.Suggested fix
Assert on what all three capacity errors share: the
CAPACITY_EXCEEDEDcategory, or the substringensure enough disk space has been allocated. Don't match the bundle-specific message, and includet.getMessage()in the assertion message so a future mismatch shows the actual error.Merged fix: #20552 (2026-10-11).
Occurrences
Failed push-triggered master jobs only. The daily triage routine adds one row per new failed job.
unit tests / unit tests(main) (25, N*,Q*) / test-jdk25-[N*,Q*]expected: <true> but was: <false>at line 166 (message lackedUnable to reserve bundle); single attempt, no surefire retryunit tests / unit tests(main) (25, N*,Q*) / test-jdk25-[N*,Q*]expected: <true> but was: <false>at line 166; single attempt, no surefire retry