-
Notifications
You must be signed in to change notification settings - Fork 194
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
Native build runs out of memory on GitHub actions when io.fabric8:openshift-client is on the classpath #5515
Labels
Milestone
Comments
Maybe something else we could try experimenting with, is adding an extra build step to use the MacOS runner. They have more memory, so we could dedicate that job to running memory hungry native builds. |
This was referenced Nov 16, 2023
Closed
jamesnetherton
added a commit
that referenced
this issue
Jan 9, 2024
jamesnetherton
added a commit
that referenced
this issue
Jan 10, 2024
jamesnetherton
added a commit
that referenced
this issue
Jan 10, 2024
jamesnetherton
added a commit
that referenced
this issue
Jan 15, 2024
jamesnetherton
added a commit
to jamesnetherton/camel-quarkus
that referenced
this issue
Jan 17, 2024
jamesnetherton
added a commit
to jamesnetherton/camel-quarkus
that referenced
this issue
Jan 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
Since Quarkus 3.6.0.CR1, native builds with
io.fabric8:openshift-client
on the classpath run out of memory on GitHub actions.camel-quarkus-integration-test-camel-k-runtime
camel-quarkus-integration-test-kubernetes
camel-quarkus-integration-test-master-openshift
There was a workaround implemented in the Quarkus test suite to exclude some problem dependencies and allow the native build to complete with a broken classpath:
quarkusio/quarkus#36312 (comment)
There's some more discussion on the topic here:
https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/kubernetes-client.20native.20build.20memory.20usage
I don't see too many options to fix it other than implementing the same workaround and maybe investigate reworking the
camel-kubernetes
component (I.e split it up or use some of the suggestions Marc mentions in the Zulip thread).The text was updated successfully, but these errors were encountered: