Skip to content

[fix][ci] Ensure disk headroom for replication tests - #26559

Merged
merlimat merged 1 commit into
apache:masterfrom
lhotari:lh-fix-replication-test-disk
Sep 13, 2026
Merged

merlimat merged 1 commit into
apache:masterfrom
lhotari:lh-fix-replication-test-disk

Conversation

@lhotari

@lhotari lhotari commented Sep 12, 2026

Copy link
Copy Markdown
Member

Motivation

Replication tests start multiple local BookKeeper ensembles. With limited free disk space, ledger directories can cross BookKeeper's disk-usage threshold and become unwritable, causing failures unrelated to the replication behavior under test.

Modifications

Run the existing disk-cleanup action for Broker Group 5 as well as resource-tracing runs. The action stops once its existing 20 GiB free-space threshold is met. Test selection, BookKeeper thresholds, Gradle caches and build artifacts are unchanged.

Verifying this change

  • Make sure that the change passes the CI checks.

spotlessCheck checkstyleMain checkstyleTest passed. Nine workflow-expression cases verified replication and non-replication groups with resource tracing off/on/full. Actionlint reports no new diagnostics relative to master. Local review found no remaining issues.

Does this pull request potentially affect one of the following parts:

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The threading model
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • The metrics
  • Anything that affects deployment

Run the existing disk cleanup for Broker Group 5 to avoid BookKeeper disk-threshold failures on runners with limited free space.

Assisted-by: Codex

@void-ptr974 void-ptr974 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@merlimat
merlimat merged commit e23f959 into apache:master Sep 13, 2026
86 of 88 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants