32793862389
44%
main: 45%

Ran 25 Aug 2026 12:40AM UTC

Jobs 1

Files 73

Run time 1min

Badge

Embed ▾

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

Build # 32793862389

Build Type

push

github

Committed by

abrarshivani

Commit Message

fix(ci): bound the diagnostic queries in the polling loops too

A diagnostic that hangs stalls its loop exactly as a decision-driving query
would, and kubectl has no per-request timeout by default, so the wall clock
deadline never gets a chance to be tested. Bound the progress prints, the log
and describe collection, and the state dumps on the timeout paths. The status
poll in test_restart_operator is bounded for the same reason, even though that
loop counts iterations rather than time; the container selection and kill are
untouched.

The existing 15s default suits a listing or a status field, not a fetch that
carries a whole object or a container log. The driver build log runs to
megabytes and now crosses the WAN, and bounding it at 15s would leave a
truncated artifact, which is the failure the log collection exists to prevent.
Add KUBECTL_LOG_TIMEOUT at 120s and use it for logs, describe, and full object
dumps, keeping the short timeout for the cheap queries.

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	32793862389.1	25 Aug 2026 12:40AM UTC	73	37.69	GitHub Action Run

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

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32793862389

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

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 32793862389

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

README BADGES
x