You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2019/10/14 20:36:20 UTC
[GitHub] [camel-quarkus] dhartford edited a comment on issue #275:
camel-quarkus-integration-test-core -Dnative outofmemory or 137 error
dhartford edited a comment on issue #275: camel-quarkus-integration-test-core -Dnative outofmemory or 137 error
URL: https://github.com/apache/camel-quarkus/issues/275#issuecomment-541902612
Thanks @ppalaga, I'm trying to go as deep as I can so the next person has more to work from --
Scenario 1: no xmx flags, default docker setup:
- FAIL: above error (out of memory)
Scenario 2: with `-Dnative-image.xmx=5g`, default docker setup:
- FAIL: Image error 137 (docker error, not a lot to run with)
Scenario 3: with `-Dnative-image.xmx=5g`,modify docker engine **memory limit** to 8g (docker->preferences->advanced)
- PASS: Tests run past above issue
Scenario 4: **without** `-Dnative-image.xmx=5g`,modify docker engine **memory limit** to 8g (docker->preferences->advanced)
- PASS: Tests run past above issue
If it wasn't for scenario 2 giving _worse_ debug information than scenario 1, could add a <nativeImageXmx>5g</nativeImageXmx> config directly in the quarkus maven plugin. However, given this is a 'how is your docker setup for maximum memory' I'm not sure how to improve the developer experience.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services