-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Avoid Compilation errors on Semeru JDK flavour. #2835
Avoid Compilation errors on Semeru JDK flavour. #2835
Conversation
@juherr - Now I saw a different error again on the same osgi dependencies (with not being able to resolve artifacts). I have pushed an additional commit here that bumps up the test versions (Hope that would fix it) https://github.com/krmahadevan/testng/actions/runs/3467189157/jobs/5791820079 JDK 11 Zulu
https://github.com/cbeust/testng/actions/runs/3467191687/jobs/5791824963 JDK17 SapMachine
|
org.testng.test.osgi.PlainOsgiTest is flaky and Randomly fails with dependency resolution on some JDK flavours and not all. So configuring the build To ignore this failure and move forward.
Hi @vlsi , we are stuck. Do you have any idea about the random issue? |
Is it reproducible? See https://github.com/pgjdbc/pgjdbc/actions/runs/3459838388/jobs/5775689519#step:8:539
As it did not fail much, I have not explored if there's a way to configure retries or something like that. |
The artifact you mention is listed on Central, so the version should not be an issue: https://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-atinject_1.0_spec/1.0/ |
@vlsi - It happens almost for every build and every time its a different artifact and confined to only one of these https://github.com/cbeust/testng/blob/a678d0586e2cf2ccf39d8997a24517c25f7be366/testng-test-osgi/testng-test-osgi-build.gradle.kts#L28-L31 and its not across all JDK flavours. Its random. I am not able to see/determine a pattern on when this happens |
I think ArtifactResolutionException is not related to Gradle build script. |
@vlsi - Any suggestions on how to get this sorted out ? |
I would suggest waiting for a couple of days and checking if that resolves on its own. |
No description provided.