-
Notifications
You must be signed in to change notification settings - Fork 3
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
Akamai SDK build timeout due to CPU/Memory starvation in GitHub Actions? #366
Comments
Hi @jooooel. I'm sorry you're hitting that issue. Profiling Akamai, it looks like it takes ~2.9GB to build Akamai. That should fall within GitHub's memory limit, but its still a lot. We hope to be able to get that down in the near future. |
Ah yes, that sounds like it could be an issue yes… do you have a recommendation about what do to in the mean time? Can I use pre built binaries for Akamai maybe? 🤔 |
You can't use a pre-built binary for Akamai (since it is a library), but you can use a pre-built binary for your pulumi program by setting the |
I “solved” it by using a larger GitHub Action runner 😅 |
That also works 😄 |
Related to pulumi/pulumi-terraform-bridge#1468. |
What happened?
I'm trying to run pulumi up/preview in GitHub Actions, but there seems to be some issues with building the Pulumi Akamai Go SDK.
The job is stuck for a really long time and it looks like nothing happens. After a while (close to an hour maybe), the job fails and I get the following error:
Example
I have narrowed it down to building
github.com/pulumi/pulumi-akamai/sdk/v6/go/akamai
. Here is a minimal reproduction. One part is amain.go
that only references the SDK. And the other part is the config for a GitHub Action that can trigger the issue.Output of
pulumi about
Not really relevant I guess...
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: