32792485724
44%
main: 45%

Ran 25 Aug 2026 12:21AM UTC

Jobs 1

Files 73

Run time 1min

Badge

Embed ▾

Committed 25 Aug 2026 12:08AM UTC coverage: 37.688%. Remained the same

Build # 32792485724

Build Type

push

github

Committed by

abrarshivani

Commit Message

fix(ci): re-query the node count until it is positive

The count of GPU nodes is resolved once and kept, because the upgrade churns
node labels and a per-iteration count could sample a transient value and match
early. The guard for that tested the cached value for emptiness, which only
holds when the query failed. A successful query returning zero, which is what
happens when no node carries the label yet, was cached like any other answer,
and the loop then compared against a frozen zero for the rest of its budget.
Cache only a positive count, so an API error and a zero both retry.

Give every kubectl call that a polling loop depends on an explicit request
timeout. kubectl defaults to no per-request timeout, and a wall clock deadline
is only tested between commands, so one hung request could run past it for as
long as the connection stayed open.

Drop the remaining explanatory comments.

Signed-off-by: Abrar Shivani <ashivani@nvidia.com>

Coverage Stats

4881 of 12951 relevant lines covered (37.69%)

0.38 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	32792485724.1	25 Aug 2026 12:21AM UTC	73	37.69	GitHub Action Run

NVIDIA / gpu-operator / 32792485724
44%
main: 45%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32792485724

NVIDIA / gpu-operator / 32792485724 44% main: 45%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32792485724

NVIDIA / gpu-operator / 32792485724
44%
main: 45%

README BADGES
x