25106292045
45%
main: 56%

Ran 29 Apr 2026 11:32AM UTC

Jobs 1

Files 20

Run time 1min

Badge

Embed ▾

Committed 29 Apr 2026 11:29AM UTC coverage: 44.658%. Remained the same

Build # 25106292045

Build Type

Pull #832

github

Committed by

yankay

Commit Message

fix: avoid 409 Conflict races in integration test status updates

The 'Test default progressing state' integration test misuses
gomega.Eventually by passing the result of k8sClient.Status().Update
directly, so Update is only invoked once and Eventually keeps
re-checking the same already-resolved error. When the reconciler
updates the LWS status concurrently, the single attempt hits a 409
Conflict and the test times out after 120s.

The SetStatefulsetToUnReady test helper has the same class of bug:
the caller does a Get first and then this helper issues a single
Status().Update on the (potentially already-stale) object, so any
concurrent reconciler write produces a 409.

Wrap both updates in an Eventually polling closure that re-Gets the
latest object on every retry and re-issues Status().Update, matching
the canonical pattern used in kueue and jobset integration tests.

Signed-off-by: Kay Yan <kay.yan@daocloud.io>

Pull Request Pull Request #832: fix: flaky 'Test default progressing state' integration test

Coverage Stats

1183 of 2649 relevant lines covered (44.66%)

3.05 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	25106292045.1	29 Apr 2026 11:32AM UTC	20	44.66	GitHub Action Run

kubernetes-sigs / lws / 25106292045
45%
main: 56%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 25106292045

kubernetes-sigs / lws / 25106292045 45% main: 56%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 25106292045

kubernetes-sigs / lws / 25106292045
45%
main: 56%

README BADGES
x