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

Use mvnw in CI to make sure we have a stable Maven version #17116

Merged
merged 1 commit into from
May 11, 2021

Conversation

gsmet
Copy link
Member

@gsmet gsmet commented May 10, 2021

No description provided.

@gsmet gsmet added this to the 1.11.7.Final milestone May 10, 2021
@quarkus-bot quarkus-bot bot added the area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure label May 10, 2021
@geoand
Copy link
Contributor

geoand commented May 10, 2021

CI failure seems related:

 ../tcks/mvnw: 219: cannot open /home/runner/work/quarkus/quarkus/resteasy-reactive-testsuite/.mvn/wrapper/maven-wrapper.properties: No such file
/home/runner/work/quarkus/quarkus/resteasy-reactive-testsuite/.mvn/wrapper/maven-wrapper.jar: No such file or directory
Error: Could not find or load main class org.apache.maven.wrapper.MavenWrapperMain
Caused by: java.lang.ClassNotFoundException: org.apache.maven.wrapper.MavenWrapperMain
Error: Process completed with exit code 1.

@famod
Copy link
Member

famod commented May 10, 2021

The easiest fix for this might be to introduce mvnw in the 1.11 branch of the testsuite...

Alternatively, switching the working-directory to tcks and using -f ../resteasy-reactive-testsuite/pom.xml could work but you might run into #16906 (not if you append pom.xml).

@gsmet
Copy link
Member Author

gsmet commented May 10, 2021

Yeah I was expected something like that. I think I haven't totally grokked the structure. What I don't understand is how you can find ../tcks/.github/mvn-settings.xml and not the Maven wrapper.

@famod
Copy link
Member

famod commented May 10, 2021

Probably a bug in the wrapper. I suppose it didn't even come as far to check the settings file.

@quarkus-bot
Copy link

quarkus-bot bot commented May 10, 2021

This workflow status is outdated as a new workflow run has been triggered.

🚫 This workflow run has been cancelled.

Failing Jobs - Building 7832ab4

⚠️ Artifacts of the workflow run were not available thus the report misses some details.

Status Name Step Test failures Logs Raw logs
JVM Tests - JDK 11 Build ⚠️ Check → Logs Raw logs
JVM Tests - JDK 11 Windows Build ⚠️ Check → Logs Raw logs
JVM Tests - JDK 15 Build ⚠️ Check → Logs Raw logs
JVM Tests - JDK 8 Build ⚠️ Check → Logs Raw logs
MicroProfile TCKs Tests Run RESTEasy Reactive TCK ⚠️ Check → Logs Raw logs
Native Tests - Misc1 Build ⚠️ Check → Logs Raw logs
Native Tests - Misc4 Build ⚠️ Check → Logs Raw logs
Native Tests - Spring Build ⚠️ Check → Logs Raw logs
Native Tests - gRPC Build ⚠️ Check → Logs Raw logs

@quarkus-bot
Copy link

quarkus-bot bot commented May 10, 2021

Failing Jobs - Building 407748a

Status Name Step Test failures Logs Raw logs
JVM Tests - JDK 11 Build Test failures Logs Raw logs
✔️ JVM Tests - JDK 15
✔️ JVM Tests - JDK 8

Full information is available in the Build summary check run.

Test Failures

⚙️ JVM Tests - JDK 11 #

📦 integration-tests/smallrye-context-propagation

io.quarkus.context.test.mutiny.MutinyContextPropagationTest.testTransactionContextPropagationMulti line 155 - More details - Source on GitHub

@gsmet gsmet merged commit 6b724df into quarkusio:1.11 May 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants