-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow failure: cron #4379
Labels
kind/engineering
Work that is not visible to an external user
p1
A bug severe enough to be the next item assigned to an engineer
Comments
pulumi-bot
added
kind/engineering
Work that is not visible to an external user
needs-triage
Needs attention from the triage team
p1
A bug severe enough to be the next item assigned to an engineer
labels
Aug 17, 2024
Building the go SDK causes out of disk space issues...
We might have to add disk space cleaning to this as well or go for bigger runners. Will look into this |
flostadler
added a commit
to pulumi/ci-mgmt
that referenced
this issue
Aug 19, 2024
Some of the workflows on larger providers like aws started failing because they're running out of disk space. Examples are: - pulumi/pulumi-aws#4379 - https://github.com/pulumi/pulumi-aws/actions/runs/10421649189/job/28864324845 This change adds a new configuration parameter (`freeDiskSpaceBeforeSdkBuild`) to free the disk space before SDK builds. Additionally it also adds the disk space cleaning to the upgrade-bridge workflow.
flostadler
added a commit
to pulumi/ci-mgmt
that referenced
this issue
Aug 19, 2024
) Some of the workflows on larger providers like aws started failing because they're running out of disk space (again.. sigh). Examples are: - pulumi/pulumi-aws#4379 - https://github.com/pulumi/pulumi-aws/actions/runs/10421649189/job/28864324845 This change adds a new configuration parameter (`freeDiskSpaceBeforeSdkBuild`) to free the disk space before SDK builds. Additionally it also adds the disk space cleaning to the upgrade-bridge workflow. We should also explore using bigger runners, but this might be cost prohibitive (AWS alone had ~1.1k build hours within the last month, which would amount to ~1k$ for a larger runner).
Will be fixed by #4381 |
This issue has been addressed in PR #4381 and shipped in release v6.50.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/engineering
Work that is not visible to an external user
p1
A bug severe enough to be the next item assigned to an engineer
Workflow Failure
cron has failed. See the list of failures below:
2024-08-17T07:03:17.000Z
2024-08-18T07:12:59.000Z
2024-08-19T07:06:00.000Z
2024-08-19T08:14:35.000Z
The text was updated successfully, but these errors were encountered: