Skip to content

Synchronise 2025.1 with upstream#558

Merged
Alex-Welsh merged 1 commit intostackhpc/2025.1from
upstream/2025.1-2026-05-04
May 5, 2026
Merged

Synchronise 2025.1 with upstream#558
Alex-Welsh merged 1 commit intostackhpc/2025.1from
upstream/2025.1-2026-05-04

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented May 4, 2026

This PR contains a snapshot of 2025.1 from upstream stable/2025.1.

Sometimes we land on a node with a 40G disk. We've seen disk space
related failures on the upgrade jobs.

Change-Id: I036d95cace1fe2083f669837c99e75e15e576032
Signed-off-by: Will Szumski <will@stackhpc.com>
@github-actions github-actions Bot added automated Automated action performed by GitHub Actions synchronisation labels May 4, 2026
@github-actions github-actions Bot requested a review from a team as a code owner May 4, 2026 07:19
@Alex-Welsh Alex-Welsh closed this May 5, 2026
@Alex-Welsh Alex-Welsh reopened this May 5, 2026
@Alex-Welsh Alex-Welsh enabled auto-merge May 5, 2026 08:10
@Alex-Welsh Alex-Welsh merged commit b9db528 into stackhpc/2025.1 May 5, 2026
4 checks passed
@Alex-Welsh Alex-Welsh deleted the upstream/2025.1-2026-05-04 branch May 5, 2026 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated action performed by GitHub Actions synchronisation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants