-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Initial problem listing for Windows ARM64 #4155
Comments
Adding to JDK17. These are issues with both 11 and 17 and fail in the same way.
|
@sophia-guo and @smlambert will this be possible for us to use and still get into the marketplace? We're coming in very late already, and this is the last set of blockers we have to get the TAP files required to pass... |
@d3r3kk - yes, the small set of remaining failing testcases can be excluded to get a clean run. Exclusions are permitted / expected, especially with new platforms as issues typically need to be worked out (and since exclusions are open, transparent and searchable), this is not a blocker for adding this platform into the marketplace I should also mention, since these exclusions are not vendor specific, they do not need to be held in the vendor exclude files, but can be added to the common ProblemList files. |
Ah ok, thank you @smlambert for the clarity! |
These are the tests included on JDK21 for Windows ARM64:
|
For April 2024 PSU we problemlisted two more test for Windows ARM64 JDK21:
|
Please let me know if this should be broken up into separate GitHub issues!
Initial problem listing for Window AArch64 for JDK11 and JDK17:
With respect to
java/foreign/*
tests there is ongoing work to update the foreign function and memory API to work with Windows ARM64 so I believe that Temurin might be affected by these tests as well.Example output:
tentative-microsoft-excludes.zip
The text was updated successfully, but these errors were encountered: