[aarch64-port-dev ] RFR: 8253795: Implementation of JEP 391: macOS/AArch64 Port
Vladimir Kempik
vkempik at openjdk.java.net
Sat Jan 8 13:29:59 UTC 2022
On Fri, 7 Jan 2022 16:13:45 GMT, Bernhard Urban-Forster <burban at openjdk.org> wrote:
>> Running fastdebug tier1 on macOS/AArch64 looks good:
>>
>> ==============================
>> Test summary
>> ==============================
>> TEST TOTAL PASS FAIL ERROR
>>>> jtreg:test/hotspot/jtreg:tier1 1239 1238 1 0 <<
>>>> jtreg:test/jdk:tier1 1872 1866 6 0 <<
>> jtreg:test/langtools:tier1 3915 3915 0 0
>> jtreg:test/nashorn:tier1 0 0 0 0
>> jtreg:test/jaxp:tier1 0 0 0 0
>> ==============================
>> TEST FAILURE
>>
>>
>> Those 6 failures in `jdk:tier` also happen on Linux/AArch64, so I'll ignore them. The hotspot failure happens on `test/hotspot/jtreg/runtime/ErrorHandling/TestOnError.java` with the following output:
>>
>>
>> TEST RESULT: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: '^Test Succeeded' missing from stdout
>>
>>
>> Not sure what's going on.
>>
>> Circeling back to the r18 issue mentioned here: https://github.com/openjdk/jdk11u-dev/pull/301#issuecomment-911998917
>> My understanding is that the current stable release of macOS (12.1 Monterey) should already be affected by this issue, as I haven't backported https://bugs.openjdk.java.net/browse/JDK-8274795 to jdk11 yet. Do you have some better reproducer other than running Intellij? Apparently none of the tier1 tests seem to trigger it.
>>
>> Edit: The `release` build of this branch actually runs Intellij just fine.
>
>> @lewurm I am also getting the same `TestOnError` failure in hotspot:tier1 when I run the tests on the fastdebug build. However, I do not get the 6 langtools failures. All tier1 tests pass on the release build though.
>
> Thanks for looking at it @ahmedmuhsin, probably an issue with my setup then.
>
>> Edit: The release build of this branch actually runs Intellij just fine.
>
> Running on that build for >48h now. Seems good (it doesn't just sit in the background, but I'm actually using it).
>
>> Is there an issue here that prevents 8274795 from being backported to 11? It's
>> obviously a bug. Are you waiting for the MacOS port?
>
> Yes, I was hoping the macOS port nicely crashes Here is the backport: https://github.com/openjdk/jdk11u-dev/pull/744
>
>
> @VladimirKempik not sure how you would like to proceed with this, do you want to merge this PR into `jdk11-macos` or do we just let it sit and bake here? Both is fine I think.
@lewurm just proceed with https://github.com/openjdk/jdk11u-dev/pull/744 it's independent of this PR
-------------
PR: https://git.openjdk.java.net/aarch64-port/pull/14
More information about the aarch64-port-dev
mailing list