Open sophia-guo opened 2 years ago
Can I work on this issue? I can update mvn to mvnw in camel script. How to see the result on update?. Will you please guide me with that?
jdk11 and jdk17 issue mentioned in https://github.com/adoptium/aqa-tests/issues/3468#issue-1171132974 has been resolved by updated to mvn wrapper. The requirement of java is jdk11.
Current issue would be rerun job to see which specific tests fail when the PR https://github.com/adoptium/aqa-tests/pull/3523/ is merged.
@sophia-guo - @abhijeetjejurkar does not currently have access to run a Grinder, but I can add him to a team that does, if you want help with this issue and assign him.
That would be great @smlambert . @abhijeetjejurkar with #3523 in we will need to rerun tests with jdk17 and jdk11 ( the minimal requirements for jdk version is 11) and update the excludeProject variable to exclude the failure tests. I already have two runs. jdk17: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/614/console jdk11: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/615/console
Both have failures. We can start from those two builds.
For example:
20:14:03 [INFO] Camel Quarkus :: Support Spring :: Integration Test FAILURE [01:27 min]
. To do that we need first to find artifactID [
@smlambert @sophia-guo Thankyou for considering me. I will work on it. I just need some time to understand the issue.
thanks @abhijeetjejurkar - you have an invitation to join a github team (AdoptOpenJDK/canosp_w22) which will give you access to running tests on our Jenkins instance. Once you accept the invitation, you should be able to login to our Jenkins server and run test jobs.
As Sophia mentions:
Update https://github.com/adoptium/aqa-tests/blob/master/external/camel/test.sh to use mvnw instead of mvn will use proper maven. We'd like to see the result with this update.
Once you make that change, you will be able to run tests on the changes from your branch. (create a branch, make the change, then trigger a 'rebuild' on the jobs that Sophia mentions above, for example:
https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/614/rebuild/parameterized but changing the ADOPTOPENJDK_REPO and ADOPTOPENJDK_BRANCH to your repo/branch.
If you have questions, please post them here or in the testing-aqavit Slack channel. :)
Thankyou ma'am for the detailed guidelines. I will follow the steps as mentioned by you.😊
Thankyou @smlambert for the detailed guidelines. I will follow the steps as mentioned by you. If I stuck somewhere I will let you know. 😊
External test /camel has updated to mvn wrapper mvnw, which means no need to install default maven. Maven wrapper will specify and installed preferred maven version 3.8.3. Currently all camel tests jdk8, 11, 17 failed.
JDK8: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/537/ error message:
Unrecognized option: --illegal-access=permit Error: Could not create the Java Virtual Machine.
JDK11: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/536/ error message:11:05:51 Detected Maven Version: 3.6.3 is not in the allowed range [3.8.1,).
JDK17: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/536/ error message:10:58:45 [[1;31mERROR[m] Error executing Maven.
Update https://github.com/adoptium/aqa-tests/blob/master/external/camel/test.sh to use mvnw instead of mvn will use proper maven. We'd like to see the result with this update.