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

"Rerun failed jdk test cases in Grinder with jdk_custom target" didn't set BUILD_LIST #4385

Closed
pshipton opened this issue Mar 2, 2023 · 3 comments · Fixed by #4398
Closed
Assignees
Labels

Comments

@pshipton
Copy link
Contributor

pshipton commented Mar 2, 2023

In the build https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_sanity.openjdk_s390x_linux_OpenJDK11/66/
The link for Rerun failed jdk test cases in Grinder with jdk_custom target
doesn't set BUILD_LIST properly. Although it does contain BUILD_LIST=openjdk, when you open the link the BUILD_LIST is set to functional.

@pshipton
Copy link
Contributor Author

pshipton commented Mar 2, 2023

@llxia
Copy link
Contributor

llxia commented Mar 3, 2023

The problematic link contains CUSTOM_TARGET=java/lang/ProcessBuilder/Basic.java#id0. The special character # breaks the URL link. The CUSTOM_TARGET value has to be encoded. See https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L1054

@sophia-guo could you fix this? Thanks

@sophia-guo
Copy link
Contributor

sophia-guo commented Mar 7, 2023

Encoding is one thing. The reason it worked on mac is the test job on mac has default BUILT_LIST=openjdk while on s390 default BUILD_LIST=functional.

The other thing is jtreg won't work when specify test case suffixed by #id/d{1,}. Update the CUSTOM_TARGET to remove that and no need to encoding it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants