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

update commons compress #282

Merged
merged 1 commit into from
Apr 13, 2020
Merged

update commons compress #282

merged 1 commit into from
Apr 13, 2020

Conversation

elharo
Copy link
Contributor

@elharo elharo commented Apr 9, 2020

@elharo elharo requested a review from michael-o April 9, 2020 19:01
@michael-o
Copy link
Member

Why does this one fail?

@elharo
Copy link
Contributor Author

elharo commented Apr 9, 2020

Looks like the build is flaky, not sure why:

[INFO] -------------------------------------------------
[ERROR] The following builds failed:
[ERROR] * jetty-war-test-passing/pom.xml
[INFO] -------------------------------------------------

@Tibor17
Copy link
Contributor

Tibor17 commented Apr 10, 2020

@elharo
You have to see the POM in Failsafe because there is maven-invoker-plugin which generates additional logs, pls see them.
It is not possible to see those logs here on GH and therefore run the build on your private machine with Ubuntu and it should also fail after 6 minutes.
These are the logs which you should check on your machine:
maven-failsafe-plugin/target/it/jetty-war-test-passing/build.log
maven-failsafe-plugin/target/it/jetty-war-test-passing/target/failsafe-reports/*.dump*

@elharo
Copy link
Contributor Author

elharo commented Apr 13, 2020

Failure is a network flake in central on one node:

[ERROR] Plugin org.codehaus.mojo:javacc-maven-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:javacc-maven-plugin:jar:2.6: Could not transfer artifact org.codehaus.mojo:mojo-parent:pom:22 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/codehaus/mojo/mojo-parent/22/mojo-parent-22.pom 503 Backend unavailable, connection timeout -> [Help 1]

@michael-o
Copy link
Member

So it should work now?

@elharo
Copy link
Contributor Author

elharo commented Apr 13, 2020

Yep, reran it and it all passed.

@elharo elharo merged commit b1f7a69 into master Apr 13, 2020
@elharo elharo deleted the pom branch April 13, 2020 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants