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

Clean up MSFT Problem list #6012

Open
karianna opened this issue Mar 7, 2025 · 1 comment
Open

Clean up MSFT Problem list #6012

karianna opened this issue Mar 7, 2025 · 1 comment
Assignees

Comments

@karianna
Copy link
Contributor

karianna commented Mar 7, 2025

          > are there any progress updates on the work on creating a main problemlist? Is there anything I can do to help?

Sorry, I thought you were actively looking at it.

For any of the entries that are already reported upstream (JBS issues), can be put in common problemlists (found in this folder https://github.com/adoptium/aqa-tests/tree/master/openjdk/excludes).

For the aqa-tests reported issues, it will be good to check if those testcases are running and failing in our weekly test jobs, If they are, those can also go into the common problemlists.

For anything that you know to be MSFT specific and where we see it running and passing against Temurin, those excludes can stay in the vendor problemlist.

I see references to some of the issues that @andrew-m-leonard reported because they were failing against Temurin and thought to be common problems, such as https://bugs.openjdk.org/browse/JDK-8348862, so I expect we already have them excluded in the common problemlists (see https://github.com/adoptium/aqa-tests/blob/master/openjdk/excludes/ProblemList_openjdk21.txt#L478 for example).

If you are running tests via TKG and our playlists, then you will already be using both the common and vendor problemlists passed to jtreg on the commandline (example: https://github.com/adoptium/aqa-tests/blob/master/openjdk/playlist.xml#L354-L357)

Noting that for JDK11, there is no Temurin windows-aarch64 build so it won't be possible to check the test jobs for that version.

Originally posted by @smlambert in #5973 (comment)

@jmjaffe37
Copy link
Contributor

I am adding a comment here, as per request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants