Skip to content
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

Remove usage of deprecated native-image mojo from amazon-lambda integration tests #11659

Merged
merged 1 commit into from
Aug 28, 2020
Merged

Conversation

jaikiran
Copy link
Member

Fixes #11655

@patriot1burke, does this work?

We will have to do similar changes for the other integration tests, but for now I think this should get @patriot1burke past the issue he's running into.

@patriot1burke
Copy link
Contributor

You don't have to add it to amazon-lambda. I was just using that as an easy way to reproduce the problem.

@geoand
Copy link
Contributor

geoand commented Aug 27, 2020

You don't have to add it to amazon-lambda. I was just using that as an easy way to reproduce the problem.

Most of the integration tests use the old way of configuring native - which likely the problem manifested for you some of the times. I think you mentioned that the problem did not occur when you used codestarts? That fits this theory perfectly

@jaikiran
Copy link
Member Author

jaikiran commented Aug 28, 2020

Merging this. The tests have all passed except the Windows Java 11 JVM one and the Data 4 Native tests, which is failing with the issue reported at #11711

@jaikiran jaikiran merged commit 4eef21d into quarkusio:master Aug 28, 2020
@jaikiran jaikiran deleted the qk-11655 branch August 28, 2020 13:24
@gsmet gsmet added this to the 1.8.0.CR1 milestone Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

auto-service-loader-registration=true does not work in quarkus/integration-tests
5 participants