Skip to content

[SPARK-58871][INFRA] Add timeout to disk cleanup steps - #58121

Closed
zhengruifeng wants to merge 1 commit into
apache:masterfrom
zhengruifeng:minor-free-disk-space-timeout
Closed

[SPARK-58871][INFRA] Add timeout to disk cleanup steps#58121
zhengruifeng wants to merge 1 commit into
apache:masterfrom
zhengruifeng:minor-free-disk-space-timeout

Conversation

@zhengruifeng

@zhengruifeng zhengruifeng commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

What changes were proposed in this pull request?

This PR adds a 10-minute timeout and continue-on-error: true to the
Free up disk space steps in the GitHub Actions build workflow.

JIRA: SPARK-58871

Why are the changes needed?

The disk cleanup step is an optimization. If it hangs, the job can spend its
entire timeout before reaching setup or tests. Continuing after the cleanup
step times out lets CI proceed with a higher disk space risk instead of
cancelling the whole job during cleanup.

For example, this CI job was cancelled while running the disk cleanup step:
https://github.com/zhengruifeng/spark/actions/runs/32230206211/job/96008694804

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Not run. This is a GitHub Actions workflow-only change.

Was this patch authored or co-authored using generative AI tooling?

Generated-by: Codex (GPT-5)

@zhengruifeng zhengruifeng changed the title [MINOR][INFRA] Add timeout to disk cleanup steps [SPARK-58871][INFRA] Add timeout to disk cleanup steps Aug 19, 2026
zhengruifeng added a commit that referenced this pull request Aug 20, 2026
### What changes were proposed in this pull request?

This PR adds a 10-minute timeout and `continue-on-error: true` to the
`Free up disk space` steps in the GitHub Actions build workflow.

JIRA: SPARK-58871

### Why are the changes needed?

The disk cleanup step is an optimization. If it hangs, the job can spend its
entire timeout before reaching setup or tests. Continuing after the cleanup
step times out lets CI proceed with a higher disk space risk instead of
cancelling the whole job during cleanup.

For example, this CI job was cancelled while running the disk cleanup step:
https://github.com/zhengruifeng/spark/actions/runs/32230206211/job/96008694804

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Not run. This is a GitHub Actions workflow-only change.

### Was this patch authored or co-authored using generative AI tooling?

Generated-by: Codex (GPT-5)

Closes #58121 from zhengruifeng/minor-free-disk-space-timeout.

Authored-by: Ruifeng Zheng <ruifengz@apache.org>
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
(cherry picked from commit d8403fe)
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
zhengruifeng added a commit that referenced this pull request Aug 20, 2026
### What changes were proposed in this pull request?

This PR adds a 10-minute timeout and `continue-on-error: true` to the
`Free up disk space` steps in the GitHub Actions build workflow.

JIRA: SPARK-58871

### Why are the changes needed?

The disk cleanup step is an optimization. If it hangs, the job can spend its
entire timeout before reaching setup or tests. Continuing after the cleanup
step times out lets CI proceed with a higher disk space risk instead of
cancelling the whole job during cleanup.

For example, this CI job was cancelled while running the disk cleanup step:
https://github.com/zhengruifeng/spark/actions/runs/32230206211/job/96008694804

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Not run. This is a GitHub Actions workflow-only change.

### Was this patch authored or co-authored using generative AI tooling?

Generated-by: Codex (GPT-5)

Closes #58121 from zhengruifeng/minor-free-disk-space-timeout.

Authored-by: Ruifeng Zheng <ruifengz@apache.org>
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
(cherry picked from commit d8403fe)
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
zhengruifeng added a commit that referenced this pull request Aug 20, 2026
### What changes were proposed in this pull request?

This PR adds a 10-minute timeout and `continue-on-error: true` to the
`Free up disk space` steps in the GitHub Actions build workflow.

JIRA: SPARK-58871

### Why are the changes needed?

The disk cleanup step is an optimization. If it hangs, the job can spend its
entire timeout before reaching setup or tests. Continuing after the cleanup
step times out lets CI proceed with a higher disk space risk instead of
cancelling the whole job during cleanup.

For example, this CI job was cancelled while running the disk cleanup step:
https://github.com/zhengruifeng/spark/actions/runs/32230206211/job/96008694804

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Not run. This is a GitHub Actions workflow-only change.

### Was this patch authored or co-authored using generative AI tooling?

Generated-by: Codex (GPT-5)

Closes #58121 from zhengruifeng/minor-free-disk-space-timeout.

Authored-by: Ruifeng Zheng <ruifengz@apache.org>
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
(cherry picked from commit d8403fe)
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
zhengruifeng added a commit that referenced this pull request Aug 20, 2026
### What changes were proposed in this pull request?

This PR adds a 10-minute timeout and `continue-on-error: true` to the
`Free up disk space` steps in the GitHub Actions build workflow.

JIRA: SPARK-58871

### Why are the changes needed?

The disk cleanup step is an optimization. If it hangs, the job can spend its
entire timeout before reaching setup or tests. Continuing after the cleanup
step times out lets CI proceed with a higher disk space risk instead of
cancelling the whole job during cleanup.

For example, this CI job was cancelled while running the disk cleanup step:
https://github.com/zhengruifeng/spark/actions/runs/32230206211/job/96008694804

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Not run. This is a GitHub Actions workflow-only change.

### Was this patch authored or co-authored using generative AI tooling?

Generated-by: Codex (GPT-5)

Closes #58121 from zhengruifeng/minor-free-disk-space-timeout.

Authored-by: Ruifeng Zheng <ruifengz@apache.org>
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
(cherry picked from commit d8403fe)
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
zhengruifeng added a commit that referenced this pull request Aug 20, 2026
### What changes were proposed in this pull request?

This PR adds a 10-minute timeout and `continue-on-error: true` to the
`Free up disk space` steps in the GitHub Actions build workflow.

JIRA: SPARK-58871

### Why are the changes needed?

The disk cleanup step is an optimization. If it hangs, the job can spend its
entire timeout before reaching setup or tests. Continuing after the cleanup
step times out lets CI proceed with a higher disk space risk instead of
cancelling the whole job during cleanup.

For example, this CI job was cancelled while running the disk cleanup step:
https://github.com/zhengruifeng/spark/actions/runs/32230206211/job/96008694804

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Not run. This is a GitHub Actions workflow-only change.

### Was this patch authored or co-authored using generative AI tooling?

Generated-by: Codex (GPT-5)

Closes #58121 from zhengruifeng/minor-free-disk-space-timeout.

Authored-by: Ruifeng Zheng <ruifengz@apache.org>
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
(cherry picked from commit d8403fe)
Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
@zhengruifeng

Copy link
Copy Markdown
Contributor Author

Merge Summary:

Posted by merge_spark_pr.py

@zhengruifeng
zhengruifeng deleted the minor-free-disk-space-timeout branch August 20, 2026 00:13
nchammas added a commit that referenced this pull request Aug 25, 2026
### What changes were proposed in this pull request?

Tolerate failures from `apt-get` remove directly. Refactor the list of packages to remove into an array. Remove the call to `apt-get update`.

### Why are the changes needed?

#53226 added the call to `update` specifically to fix intermittent failures when calling `remove`.

That `update`, however, had its own issues and hit up against actions/runner-images#14594. This in turn triggered the addition of a timeout to the cleanup in #58121.

If we tolerate `remove` failures directly, we don't need the `update` anymore. I don't think we need the timeout either, but I've left that alone.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

CI on this PR.

### Was this patch authored or co-authored using generative AI tooling?

I wrote this with assistance from GitHub Copilot.

Closes #58206 from nchammas/free-disk-space-cleanup.

Authored-by: Nicholas Chammas <nicholas.chammas@gmail.com>
Signed-off-by: Nicholas Chammas <nicholas.chammas@gmail.com>
nchammas added a commit that referenced this pull request Aug 25, 2026
### What changes were proposed in this pull request?

Tolerate failures from `apt-get` remove directly. Refactor the list of packages to remove into an array. Remove the call to `apt-get update`.

### Why are the changes needed?

#53226 added the call to `update` specifically to fix intermittent failures when calling `remove`.

That `update`, however, had its own issues and hit up against actions/runner-images#14594. This in turn triggered the addition of a timeout to the cleanup in #58121.

If we tolerate `remove` failures directly, we don't need the `update` anymore. I don't think we need the timeout either, but I've left that alone.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

CI on this PR.

### Was this patch authored or co-authored using generative AI tooling?

I wrote this with assistance from GitHub Copilot.

Closes #58206 from nchammas/free-disk-space-cleanup.

Authored-by: Nicholas Chammas <nicholas.chammas@gmail.com>
Signed-off-by: Nicholas Chammas <nicholas.chammas@gmail.com>
(cherry picked from commit 6f89924)
Signed-off-by: Nicholas Chammas <nicholas.chammas@gmail.com>
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.

5 participants