Skip to content

gha: set timeouts for buildkit tests#50823

Draft
thaJeztah wants to merge 1 commit intomoby:masterfrom
thaJeztah:buildkit_timeouts
Draft

gha: set timeouts for buildkit tests#50823
thaJeztah wants to merge 1 commit intomoby:masterfrom
thaJeztah:buildkit_timeouts

Conversation

@thaJeztah
Copy link
Member

The Windows tests sometimes hang until they reach the timeout, but a normal run seems to be ~20 minutes, so adding a 30 minute timeout as it's easier to start it again than having to wait for more than an Hour to see it failed.

- Human readable description for the release notes

- A picture of a cute animal (not mandatory but encouraged)

The Windows tests sometimes hang until they reach the timeout, but
a normal run seems to be ~20 minutes, so adding a 30 minute timeout
as it's easier to start it again than having to wait for more than
an Hour to see it failed.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
@thaJeztah thaJeztah added kind/enhancement Enhancements are not bugs or new features but can improve usability or performance. area/testing labels Aug 27, 2025
@thaJeztah thaJeztah added this to the 29.0.0 milestone Aug 27, 2025
@thaJeztah
Copy link
Member Author

FWIW; added timeouts both for Linux and Windows; not sure if they're in the right spot, but this is an example of a check hanging; https://github.com/moby/moby/actions/runs/17262067500/job/48986448717?pr=50821

cc @crazy-max

fi
echo "TESTFLAGS=${testFlags}" >> $GITHUB_ENV
- name: Test
timeout-minutes: 30
Copy link
Member

Choose a reason for hiding this comment

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

I think we should update

TESTFLAGS: "-v --timeout=90m"
to 30 instead.

Copy link
Member

Choose a reason for hiding this comment

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

And put maybe 40 in

timeout-minutes: 120 # guardrails timeout for the whole job
for the whole job.

Copy link
Member

Choose a reason for hiding this comment

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

On BuildKit repo we set the timeout to 60 in test flags: https://github.com/moby/buildkit/blob/070d993324ee4f90c0517ca70229dcffa37c270a/.github/workflows/test-os.yml#L81

So maybe for whole job 70?

*.output=type=docker,name=${{ env.TEST_IMAGE_ID }}
-
name: Test
timeout-minutes: 30
Copy link
Member

Choose a reason for hiding this comment

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

Don't think we should for linux and this is already covered by

TESTFLAGS: "-v --parallel=1 --timeout=30m --run=//worker=${{ matrix.worker }}$"
iiuc.

If somehow the runner hangs on Linux like it happens sometimes on Windows, we should update

timeout-minutes: 120 # guardrails timeout for the whole job
to 40 instead imo.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah, good call; I missed the --timeout flags; I'll have a look at those. Mostly want to make sure we don't spend hours waiting for something we know is gonna fail 😂

@vvoland vvoland modified the milestones: 29.0.0, 29.1.0 Nov 10, 2025
@vvoland vvoland modified the milestones: 29.1.0, v-future Nov 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/testing kind/enhancement Enhancements are not bugs or new features but can improve usability or performance. process/cherry-pick/28.x

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants