Re: jdk10 on macOS

[Jonathan Gibbons]

On 01/18/2018 05:51 PM, David Holmes wrote:

On 19/01/2018 3:20 AM, Alan Snyder wrote:
I tried building from the jdk repo (vs jdk10). The 
StringPlatformChars test passed. The other four tests appear to have 
been removed.


However, I did get failures on these tests:

• MethodHandleConstants (internal error: appendix)

> • MethodReferenceTestMethodHandle (internal error: appendix)

https://bugs.openjdk.java.net/browse/JDK-8194963


• JavadocHelperTest (out of memory — Java heap space)


Common problem with javadoc.


Regrettably true, but that's not the problem in this case.The test 
is a jshell test that is analysing doc-comments, but without using the 
javadoc tool.


The heap needs to be increased. I've encountered the problem myself and 
already raised the issue with the JShell folk.


-- Jon



David



On Jan 17, 2018, at 2:24 PM, David Holmes  
wrote:


Alan,

On 18/01/2018 6:52 AM, Alan Snyder wrote:

To summarize, these are the test failures/errors:
• StringPlatformChars (error — native code not found)


This seems potentially a makefile issue.


• NewUnsafeString (did not use provided string)
• APIExtraction (class file for TestClass not found)
• ClassDependenciesTest (assertion error — null pointer in 
loadClass)

• IgnoreSymbolFile (package sun.reflect.annotation is not visible)


Any other test failures should be taken up with the component area 
related to the test - and you can also search the bug systems for 
references to such failures. Not all tests are guaranteed to always 
pass in every environment - though the intent for tier1/2 tests that 
(unless excluded via the ProblemList.txt file, or marked 
"intermittent") they do pass.


David

Re: jdk10 on macOS

[David Holmes]

On 19/01/2018 3:20 AM, Alan Snyder wrote:

I tried building from the jdk repo (vs jdk10). The StringPlatformChars test 
passed. The other four tests appear to have been removed.

However, I did get failures on these tests:

• MethodHandleConstants (internal error: appendix)

>• MethodReferenceTestMethodHandle (internal error: appendix)

https://bugs.openjdk.java.net/browse/JDK-8194963


• JavadocHelperTest (out of memory — Java heap space)


Common problem with javadoc.

David




On Jan 17, 2018, at 2:24 PM, David Holmes  wrote:

Alan,

On 18/01/2018 6:52 AM, Alan Snyder wrote:

To summarize, these are the test failures/errors:
• StringPlatformChars (error — native code not found)


This seems potentially a makefile issue.


• NewUnsafeString (did not use provided string)
• APIExtraction (class file for TestClass not found)
• ClassDependenciesTest (assertion error — null pointer in loadClass)
• IgnoreSymbolFile (package sun.reflect.annotation is not visible)


Any other test failures should be taken up with the component area related to the test - 
and you can also search the bug systems for references to such failures. Not all tests 
are guaranteed to always pass in every environment - though the intent for tier1/2 tests 
that (unless excluded via the ProblemList.txt file, or marked "intermittent") 
they do pass.

David

Re: jdk10 on macOS

[Alan Snyder]

I tried building from the jdk repo (vs jdk10). The StringPlatformChars test 
passed. The other four tests appear to have been removed.

However, I did get failures on these tests:

• MethodHandleConstants (internal error: appendix)
• JavadocHelperTest (out of memory — Java heap space)
• MethodReferenceTestMethodHandle (internal error: appendix)


> On Jan 17, 2018, at 2:24 PM, David Holmes  wrote:
> 
> Alan,
> 
> On 18/01/2018 6:52 AM, Alan Snyder wrote:
>> To summarize, these are the test failures/errors:
>>  • StringPlatformChars (error — native code not found)
> 
> This seems potentially a makefile issue.
> 
>>  • NewUnsafeString (did not use provided string)
>>  • APIExtraction (class file for TestClass not found)
>>  • ClassDependenciesTest (assertion error — null pointer in loadClass)
>>  • IgnoreSymbolFile (package sun.reflect.annotation is not visible)
> 
> Any other test failures should be taken up with the component area related to 
> the test - and you can also search the bug systems for references to such 
> failures. Not all tests are guaranteed to always pass in every environment - 
> though the intent for tier1/2 tests that (unless excluded via the 
> ProblemList.txt file, or marked "intermittent") they do pass.
> 
> David

Re: jdk10 on macOS

[David Holmes]

Alan,

On 18/01/2018 6:52 AM, Alan Snyder wrote:

To summarize, these are the test failures/errors:

• StringPlatformChars (error — native code not found)


This seems potentially a makefile issue.


• NewUnsafeString (did not use provided string)
• APIExtraction (class file for TestClass not found)
• ClassDependenciesTest (assertion error — null pointer in loadClass)
• IgnoreSymbolFile (package sun.reflect.annotation is not visible)


Any other test failures should be taken up with the component area 
related to the test - and you can also search the bug systems for 
references to such failures. Not all tests are guaranteed to always pass 
in every environment - though the intent for tier1/2 tests that (unless 
excluded via the ProblemList.txt file, or marked "intermittent") they do 
pass.


David

Re: jdk10 on macOS

[Alan Snyder]

To summarize, these are the test failures/errors:

• StringPlatformChars (error — native code not found)
• NewUnsafeString (did not use provided string)
• APIExtraction (class file for TestClass not found)
• ClassDependenciesTest (assertion error — null pointer in loadClass)
• IgnoreSymbolFile (package sun.reflect.annotation is not visible)

Re: jdk10 on macOS

[Alan Snyder]

I started from scratch using the sledgehammer approach and got the same results.



> On Jan 17, 2018, at 4:16 AM, Magnus Ihse Bursie 
>  wrote:
> 
> 
> On 2018-01-16 17:28, Alan Snyder wrote:
>> Is there some resolution to this?
>> 
>> Is the JDK that I built valid despite the test failures?
>> 
>> Are there problems with some tests or with the test scripts? If so, will the 
>> problems be fixed?
> 
> I believe the problem is most likely to reside in your environment, or 
> details on how you are building and testing, not in the build system per se. 
> On the other hand, I'm currently having multiple issues myself when trying to 
> do just a "make images && make run-test-tier1" on my machine when I tried to 
> reproduce your problem. It is not clear to me what is causing this, but at 
> least one was due to too high parallelism. The test concurrency has been 
> tweaked lately, but only with our build and test farms in mind. We should 
> definitely look into that testing on a developer machine still works out of 
> the box.
> 
> I cannot comment on the validity of the build despite the test failures. It 
> seems likely that the test failures are due to problems running the tests, 
> rather than indicating issues with the built JDK, but there's no way to be 
> sure.
> 
> Have you tried the "sledgehammer approach" from doc/building.md, i.e. 
> removing the forest and re-cloning it? At least, try to make a make 
> clean-dist and re-run everything (make images, make run-test TEST="tier1"). 
> Please check that a test image is indeed in the build/*/images directory 
> after running "make run-test". I'm still confused as to why jtreg does not 
> find the test image. That's really odd, even if there is potentially more 
> issues involved.
> 
> /Magnus
> 
>> 
>> 
>>> On Jan 9, 2018, at 9:39 AM, Alan Snyder  wrote:
>>> 
>>> I already tried make test-image; make run-test-tier1 and it had no impact 
>>> on the outcome. Given that, do you still want me to try your suggestion?
>>> 
>>>  Alan
>>> 
>>> 
 On Jan 8, 2018, at 11:28 PM, Magnus Ihse Bursie 
  wrote:
 
 
> 8 jan. 2018 kl. 23:23 skrev David Holmes :
> 
>> On 9/01/2018 4:35 AM, Jonathan Gibbons wrote:
>> Maybe the Makefile targets to run tests could report an up-front warning 
>> if the native libraries have not been built.
> Based on my observations the makefile target will also build the 
> test-image if needed.
 That's the idea, yes. However I'm afraid there might be a bug wrt this 
 when using the generated "run-test-*" targets, as opposed to the generic 
 "run-test" target. :(
 
 Alan, can you try running "make run-test TEST=tier1" instead? This should 
 definitely pull in the generation of the test image.
 
 I also do apologize that the simple build README instructions did not work 
 out of the box. :(
 
 /Magnus
 
> David
> 
>> A more advanced solution would be to use jtreg to determine if any 
>> native tests will be run (using some combination of `-k native` and 
>> `-listtests`) and if any such tests are found, then require the library 
>> to be available.
>> -- Jon
>> On 01/05/2018 06:37 PM, Alan Snyder wrote:
>>> Following the instructions for the impatient, I did make images and 
>>> then make run-test-tier1.
>>> Then after replacing the jtreg with the one Jon recommended, I did make 
>>> run-test-tier1 again.
>>> 
>>>  Alan
>>> 
>>> 
 On Jan 5, 2018, at 6:32 PM, David Holmes  
 wrote:
 
 On 6/01/2018 12:05 PM, Alan Snyder wrote:
> The tests were run via make.
 How exactly? And did you do "make test-image" first?
 
 David
 
>> On Jan 5, 2018, at 4:13 PM, David Holmes  
>> wrote:
>> 
>> Alan,
>> 
>> Unclear how you ran the tests, but:
>> 
>> TEST RESULT: Error. Use -nativepath to specify the location of 
>> native code
>> 
>> indicates jtreg was not passed the -nativepath flag. That may or may 
>> not be a build issue depending on whether the tests were executed 
>> directly or via "make".
>> 
>> Cheers,
>> David
>> 
>>> On 6/01/2018 8:43 AM, Alan Snyder wrote:
>>> 5 test failures remain using jtreg-4.2.0-tip:
>>> --
>>> TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
>>> TEST JDK: 
>>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
>>> ACTION: build -- Passed. Build successful
>>> REASON: Named class compiled on demand
>>> TIME: 1.179 seconds
>>> messages:
>>> command: build StringPlatformChars
>>> reason: Named class compiled on demand
>>> Test directory:
>>> compile: StringPlatformChars
>

Re: jdk10 on macOS

[Alan Snyder]

Regarding your last point, it seems that the test image has been built, so 
perhaps the problem lies elsewhere.

Alans-iMac:jdk10 alan$ ll build/*/images
total 3344
drwxr-xr-x  81 alan  staff 2754 Jan  5 10:41 gengraphs
drwxr-xr-x  11 alan  staff  374 Jan  5 10:42 jdk
drwxr-xr-x   3 alan  staff  102 Jan  5 10:42 jdk-bundle
drwxr-xr-x  77 alan  staff 2618 Jan  5 10:41 jmods
drwxr-xr-x   8 alan  staff  272 Jan  5 10:41 jre
drwxr-xr-x   3 alan  staff  102 Jan  5 10:42 jre-bundle
-rw-r--r--   1 alan  staff  1709015 Jan  5 10:38 sec-bin.zip
drwxr-xr-x   6 alan  staff  204 Jan  5 11:01 test
Alans-iMac:jdk10 alan$ ll build/*/images/test
total 8
-rw-r--r--  1 alan  staff   15 Jan  8 15:58 Readme.txt
drwxr-xr-x  3 alan  staff  102 Jan  5 11:00 failure_handler
drwxr-xr-x  4 alan  staff  136 Jan  5 11:01 hotspot
drwxr-xr-x  4 alan  staff  136 Jan  5 11:01 jdk



> On Jan 17, 2018, at 4:16 AM, Magnus Ihse Bursie 
>  wrote:
> 
> 
> On 2018-01-16 17:28, Alan Snyder wrote:
>> Is there some resolution to this?
>> 
>> Is the JDK that I built valid despite the test failures?
>> 
>> Are there problems with some tests or with the test scripts? If so, will the 
>> problems be fixed?
> 
> I believe the problem is most likely to reside in your environment, or 
> details on how you are building and testing, not in the build system per se. 
> On the other hand, I'm currently having multiple issues myself when trying to 
> do just a "make images && make run-test-tier1" on my machine when I tried to 
> reproduce your problem. It is not clear to me what is causing this, but at 
> least one was due to too high parallelism. The test concurrency has been 
> tweaked lately, but only with our build and test farms in mind. We should 
> definitely look into that testing on a developer machine still works out of 
> the box.
> 
> I cannot comment on the validity of the build despite the test failures. It 
> seems likely that the test failures are due to problems running the tests, 
> rather than indicating issues with the built JDK, but there's no way to be 
> sure.
> 
> Have you tried the "sledgehammer approach" from doc/building.md, i.e. 
> removing the forest and re-cloning it? At least, try to make a make 
> clean-dist and re-run everything (make images, make run-test TEST="tier1"). 
> Please check that a test image is indeed in the build/*/images directory 
> after running "make run-test". I'm still confused as to why jtreg does not 
> find the test image. That's really odd, even if there is potentially more 
> issues involved.
> 
> /Magnus
> 
>> 
>> 
>>> On Jan 9, 2018, at 9:39 AM, Alan Snyder  wrote:
>>> 
>>> I already tried make test-image; make run-test-tier1 and it had no impact 
>>> on the outcome. Given that, do you still want me to try your suggestion?
>>> 
>>>  Alan
>>> 
>>> 
 On Jan 8, 2018, at 11:28 PM, Magnus Ihse Bursie 
  wrote:
 
 
> 8 jan. 2018 kl. 23:23 skrev David Holmes :
> 
>> On 9/01/2018 4:35 AM, Jonathan Gibbons wrote:
>> Maybe the Makefile targets to run tests could report an up-front warning 
>> if the native libraries have not been built.
> Based on my observations the makefile target will also build the 
> test-image if needed.
 That's the idea, yes. However I'm afraid there might be a bug wrt this 
 when using the generated "run-test-*" targets, as opposed to the generic 
 "run-test" target. :(
 
 Alan, can you try running "make run-test TEST=tier1" instead? This should 
 definitely pull in the generation of the test image.
 
 I also do apologize that the simple build README instructions did not work 
 out of the box. :(
 
 /Magnus
 
> David
> 
>> A more advanced solution would be to use jtreg to determine if any 
>> native tests will be run (using some combination of `-k native` and 
>> `-listtests`) and if any such tests are found, then require the library 
>> to be available.
>> -- Jon
>> On 01/05/2018 06:37 PM, Alan Snyder wrote:
>>> Following the instructions for the impatient, I did make images and 
>>> then make run-test-tier1.
>>> Then after replacing the jtreg with the one Jon recommended, I did make 
>>> run-test-tier1 again.
>>> 
>>>  Alan
>>> 
>>> 
 On Jan 5, 2018, at 6:32 PM, David Holmes  
 wrote:
 
 On 6/01/2018 12:05 PM, Alan Snyder wrote:
> The tests were run via make.
 How exactly? And did you do "make test-image" first?
 
 David
 
>> On Jan 5, 2018, at 4:13 PM, David Holmes  
>> wrote:
>> 
>> Alan,
>> 
>> Unclear how you ran the tests, but:
>> 
>> TEST RESULT: Error. Use -nativepath to specify the location of 
>> native code
>> 
>> indicates jtreg was not passed the -nativepath flag. That may or may 
>> not be a build issue depending on whether t

Re: jdk10 on macOS

[Magnus Ihse Bursie]

On 2018-01-16 17:28, Alan Snyder wrote:

Is there some resolution to this?

Is the JDK that I built valid despite the test failures?

Are there problems with some tests or with the test scripts? If so, will the 
problems be fixed?


I believe the problem is most likely to reside in your environment, or 
details on how you are building and testing, not in the build system per 
se. On the other hand, I'm currently having multiple issues myself when 
trying to do just a "make images && make run-test-tier1" on my machine 
when I tried to reproduce your problem. It is not clear to me what is 
causing this, but at least one was due to too high parallelism. The test 
concurrency has been tweaked lately, but only with our build and test 
farms in mind. We should definitely look into that testing on a 
developer machine still works out of the box.


I cannot comment on the validity of the build despite the test failures. 
It seems likely that the test failures are due to problems running the 
tests, rather than indicating issues with the built JDK, but there's no 
way to be sure.


Have you tried the "sledgehammer approach" from doc/building.md, i.e. 
removing the forest and re-cloning it? At least, try to make a make 
clean-dist and re-run everything (make images, make run-test 
TEST="tier1"). Please check that a test image is indeed in the 
build/*/images directory after running "make run-test". I'm still 
confused as to why jtreg does not find the test image. That's really 
odd, even if there is potentially more issues involved.


/Magnus





On Jan 9, 2018, at 9:39 AM, Alan Snyder  wrote:

I already tried make test-image; make run-test-tier1 and it had no impact on 
the outcome. Given that, do you still want me to try your suggestion?

  Alan



On Jan 8, 2018, at 11:28 PM, Magnus Ihse Bursie  
wrote:



8 jan. 2018 kl. 23:23 skrev David Holmes :


On 9/01/2018 4:35 AM, Jonathan Gibbons wrote:
Maybe the Makefile targets to run tests could report an up-front warning if the 
native libraries have not been built.

Based on my observations the makefile target will also build the test-image if 
needed.

That's the idea, yes. However I'm afraid there might be a bug wrt this when using the generated 
"run-test-*" targets, as opposed to the generic "run-test" target. :(

Alan, can you try running "make run-test TEST=tier1" instead? This should 
definitely pull in the generation of the test image.

I also do apologize that the simple build README instructions did not work out 
of the box. :(

/Magnus


David


A more advanced solution would be to use jtreg to determine if any native tests 
will be run (using some combination of `-k native` and `-listtests`) and if any 
such tests are found, then require the library to be available.
-- Jon
On 01/05/2018 06:37 PM, Alan Snyder wrote:

Following the instructions for the impatient, I did make images and then make 
run-test-tier1.
Then after replacing the jtreg with the one Jon recommended, I did make 
run-test-tier1 again.

  Alan



On Jan 5, 2018, at 6:32 PM, David Holmes  wrote:

On 6/01/2018 12:05 PM, Alan Snyder wrote:

The tests were run via make.

How exactly? And did you do "make test-image" first?

David


On Jan 5, 2018, at 4:13 PM, David Holmes  wrote:

Alan,

Unclear how you ran the tests, but:

TEST RESULT: Error. Use -nativepath to specify the location of native code

indicates jtreg was not passed the -nativepath flag. That may or may not be a build issue 
depending on whether the tests were executed directly or via "make".

Cheers,
David


On 6/01/2018 8:43 AM, Alan Snyder wrote:
5 test failures remain using jtreg-4.2.0-tip:
--
TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
ACTION: build -- Passed. Build successful
REASON: Named class compiled on demand
TIME: 1.179 seconds
messages:
command: build StringPlatformChars
reason: Named class compiled on demand
Test directory:
compile: StringPlatformChars
elapsed time (seconds): 1.179
ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME: 0.626 seconds
messages:
command: compile 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
reason: .class file out of date or does not exist
Mode: agentvm
Agent id: 1
elapsed time (seconds): 0.626
configuration:
Boot Layer (javac runtime environment)
class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
/Users/alan/javalib/share/jtreg/lib/jtreg.jar
patch: java.base 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base
javac compilation environment
source path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
class path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/t

Re: jdk10 on macOS

[Alan Snyder]

Is there some resolution to this?

Is the JDK that I built valid despite the test failures?

Are there problems with some tests or with the test scripts? If so, will the 
problems be fixed?


> On Jan 9, 2018, at 9:39 AM, Alan Snyder  wrote:
> 
> I already tried make test-image; make run-test-tier1 and it had no impact on 
> the outcome. Given that, do you still want me to try your suggestion?
> 
>  Alan
> 
> 
>> On Jan 8, 2018, at 11:28 PM, Magnus Ihse Bursie 
>>  wrote:
>> 
>> 
>>> 8 jan. 2018 kl. 23:23 skrev David Holmes :
>>> 
 On 9/01/2018 4:35 AM, Jonathan Gibbons wrote:
 Maybe the Makefile targets to run tests could report an up-front warning 
 if the native libraries have not been built.
>>> 
>>> Based on my observations the makefile target will also build the test-image 
>>> if needed.
>> 
>> That's the idea, yes. However I'm afraid there might be a bug wrt this when 
>> using the generated "run-test-*" targets, as opposed to the generic 
>> "run-test" target. :(
>> 
>> Alan, can you try running "make run-test TEST=tier1" instead? This should 
>> definitely pull in the generation of the test image. 
>> 
>> I also do apologize that the simple build README instructions did not work 
>> out of the box. :(
>> 
>> /Magnus
>> 
>>> 
>>> David
>>> 
 A more advanced solution would be to use jtreg to determine if any native 
 tests will be run (using some combination of `-k native` and `-listtests`) 
 and if any such tests are found, then require the library to be available.
 -- Jon
 On 01/05/2018 06:37 PM, Alan Snyder wrote:
> Following the instructions for the impatient, I did make images and then 
> make run-test-tier1.
> Then after replacing the jtreg with the one Jon recommended, I did make 
> run-test-tier1 again.
> 
>  Alan
> 
> 
>> On Jan 5, 2018, at 6:32 PM, David Holmes  wrote:
>> 
>> On 6/01/2018 12:05 PM, Alan Snyder wrote:
>>> The tests were run via make.
>> How exactly? And did you do "make test-image" first?
>> 
>> David
>> 
 On Jan 5, 2018, at 4:13 PM, David Holmes  
 wrote:
 
 Alan,
 
 Unclear how you ran the tests, but:
 
 TEST RESULT: Error. Use -nativepath to specify the location of native 
 code
 
 indicates jtreg was not passed the -nativepath flag. That may or may 
 not be a build issue depending on whether the tests were executed 
 directly or via "make".
 
 Cheers,
 David
 
> On 6/01/2018 8:43 AM, Alan Snyder wrote:
> 5 test failures remain using jtreg-4.2.0-tip:
> --
> TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
> TEST JDK: 
> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
>  
> ACTION: build -- Passed. Build successful
> REASON: Named class compiled on demand
> TIME: 1.179 seconds
> messages:
> command: build StringPlatformChars
> reason: Named class compiled on demand
> Test directory:
> compile: StringPlatformChars
> elapsed time (seconds): 1.179
> ACTION: compile -- Passed. Compilation successful
> REASON: .class file out of date or does not exist
> TIME: 0.626 seconds
> messages:
> command: compile 
> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
>  
> reason: .class file out of date or does not exist
> Mode: agentvm
> Agent id: 1
> elapsed time (seconds): 0.626
> configuration:
> Boot Layer (javac runtime environment)
> class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
> /Users/alan/javalib/share/jtreg/lib/jtreg.jar
> patch: java.base 
> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base
>  
> javac compilation environment
> source path: 
> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
> class path: 
> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
>  
> rerun:
> cd 
> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
>  && \
> HOME=/Users/alan \
> JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \
> LANG=en_US.UTF-8 \
> LC_ALL=en_US.UTF-8 \
> PATH=/bin:/usr/bin \
> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-serve

Re: jdk10 on macOS

[Alan Snyder]

I already tried make test-image; make run-test-tier1 and it had no impact on 
the outcome. Given that, do you still want me to try your suggestion?

  Alan


> On Jan 8, 2018, at 11:28 PM, Magnus Ihse Bursie 
>  wrote:
> 
> 
>> 8 jan. 2018 kl. 23:23 skrev David Holmes :
>> 
>>> On 9/01/2018 4:35 AM, Jonathan Gibbons wrote:
>>> Maybe the Makefile targets to run tests could report an up-front warning if 
>>> the native libraries have not been built.
>> 
>> Based on my observations the makefile target will also build the test-image 
>> if needed.
> 
> That's the idea, yes. However I'm afraid there might be a bug wrt this when 
> using the generated "run-test-*" targets, as opposed to the generic 
> "run-test" target. :(
> 
> Alan, can you try running "make run-test TEST=tier1" instead? This should 
> definitely pull in the generation of the test image. 
> 
> I also do apologize that the simple build README instructions did not work 
> out of the box. :(
> 
> /Magnus
> 
>> 
>> David
>> 
>>> A more advanced solution would be to use jtreg to determine if any native 
>>> tests will be run (using some combination of `-k native` and `-listtests`) 
>>> and if any such tests are found, then require the library to be available.
>>> -- Jon
>>> On 01/05/2018 06:37 PM, Alan Snyder wrote:
 Following the instructions for the impatient, I did make images and then 
 make run-test-tier1.
 Then after replacing the jtreg with the one Jon recommended, I did make 
 run-test-tier1 again.
 
   Alan
 
 
> On Jan 5, 2018, at 6:32 PM, David Holmes  wrote:
> 
> On 6/01/2018 12:05 PM, Alan Snyder wrote:
>> The tests were run via make.
> How exactly? And did you do "make test-image" first?
> 
> David
> 
>>> On Jan 5, 2018, at 4:13 PM, David Holmes  
>>> wrote:
>>> 
>>> Alan,
>>> 
>>> Unclear how you ran the tests, but:
>>> 
>>> TEST RESULT: Error. Use -nativepath to specify the location of native 
>>> code
>>> 
>>> indicates jtreg was not passed the -nativepath flag. That may or may 
>>> not be a build issue depending on whether the tests were executed 
>>> directly or via "make".
>>> 
>>> Cheers,
>>> David
>>> 
 On 6/01/2018 8:43 AM, Alan Snyder wrote:
 5 test failures remain using jtreg-4.2.0-tip:
 --
 TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
 TEST JDK: 
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
  
 ACTION: build -- Passed. Build successful
 REASON: Named class compiled on demand
 TIME: 1.179 seconds
 messages:
 command: build StringPlatformChars
 reason: Named class compiled on demand
 Test directory:
 compile: StringPlatformChars
 elapsed time (seconds): 1.179
 ACTION: compile -- Passed. Compilation successful
 REASON: .class file out of date or does not exist
 TIME: 0.626 seconds
 messages:
 command: compile 
 /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
  
 reason: .class file out of date or does not exist
 Mode: agentvm
 Agent id: 1
 elapsed time (seconds): 0.626
 configuration:
 Boot Layer (javac runtime environment)
 class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
 /Users/alan/javalib/share/jtreg/lib/jtreg.jar
 patch: java.base 
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base
  
 javac compilation environment
 source path: 
 /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 class path: 
 /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
  
 rerun:
 cd 
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
  && \
 HOME=/Users/alan \
 JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \
 LANG=en_US.UTF-8 \
 LC_ALL=en_US.UTF-8 \
 PATH=/bin:/usr/bin \
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
  \
 -J-Xmx512m \
 -J-XX:MaxRAMPercentage=3 \
 -J-ea \
 -J-esa \
 -J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk1

Re: jdk10 on macOS

[Magnus Ihse Bursie]

> 8 jan. 2018 kl. 23:23 skrev David Holmes :
> 
>> On 9/01/2018 4:35 AM, Jonathan Gibbons wrote:
>> Maybe the Makefile targets to run tests could report an up-front warning if 
>> the native libraries have not been built.
> 
> Based on my observations the makefile target will also build the test-image 
> if needed.

That's the idea, yes. However I'm afraid there might be a bug wrt this when 
using the generated "run-test-*" targets, as opposed to the generic "run-test" 
target. :(

Alan, can you try running "make run-test TEST=tier1" instead? This should 
definitely pull in the generation of the test image. 

I also do apologize that the simple build README instructions did not work out 
of the box. :(

/Magnus

> 
> David
> 
>> A more advanced solution would be to use jtreg to determine if any native 
>> tests will be run (using some combination of `-k native` and `-listtests`) 
>> and if any such tests are found, then require the library to be available.
>> -- Jon
>> On 01/05/2018 06:37 PM, Alan Snyder wrote:
>>> Following the instructions for the impatient, I did make images and then 
>>> make run-test-tier1.
>>> Then after replacing the jtreg with the one Jon recommended, I did make 
>>> run-test-tier1 again.
>>> 
>>>Alan
>>> 
>>> 
 On Jan 5, 2018, at 6:32 PM, David Holmes  wrote:
 
 On 6/01/2018 12:05 PM, Alan Snyder wrote:
> The tests were run via make.
 How exactly? And did you do "make test-image" first?
 
 David
 
>> On Jan 5, 2018, at 4:13 PM, David Holmes  wrote:
>> 
>> Alan,
>> 
>> Unclear how you ran the tests, but:
>> 
>> TEST RESULT: Error. Use -nativepath to specify the location of native 
>> code
>> 
>> indicates jtreg was not passed the -nativepath flag. That may or may not 
>> be a build issue depending on whether the tests were executed directly 
>> or via "make".
>> 
>> Cheers,
>> David
>> 
>>> On 6/01/2018 8:43 AM, Alan Snyder wrote:
>>> 5 test failures remain using jtreg-4.2.0-tip:
>>> --
>>> TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
>>> TEST JDK: 
>>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
>>>  
>>> ACTION: build -- Passed. Build successful
>>> REASON: Named class compiled on demand
>>> TIME: 1.179 seconds
>>> messages:
>>> command: build StringPlatformChars
>>> reason: Named class compiled on demand
>>> Test directory:
>>> compile: StringPlatformChars
>>> elapsed time (seconds): 1.179
>>> ACTION: compile -- Passed. Compilation successful
>>> REASON: .class file out of date or does not exist
>>> TIME: 0.626 seconds
>>> messages:
>>> command: compile 
>>> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
>>>  
>>> reason: .class file out of date or does not exist
>>> Mode: agentvm
>>> Agent id: 1
>>> elapsed time (seconds): 0.626
>>> configuration:
>>> Boot Layer (javac runtime environment)
>>> class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
>>> /Users/alan/javalib/share/jtreg/lib/jtreg.jar
>>> patch: java.base 
>>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base
>>>  
>>> javac compilation environment
>>> source path: 
>>> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>>> class path: 
>>> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
>>>  
>>> rerun:
>>> cd 
>>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
>>>  && \
>>> HOME=/Users/alan \
>>> JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \
>>> LANG=en_US.UTF-8 \
>>> LC_ALL=en_US.UTF-8 \
>>> PATH=/bin:/usr/bin \
>>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
>>>  \
>>> -J-Xmx512m \
>>> -J-XX:MaxRAMPercentage=3 \
>>> -J-ea \
>>> -J-esa \
>>> -J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>>>  \
>>> -J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>>>  \
>>> -J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>>>  \
>>> -J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A

Re: jdk10 on macOS

[David Holmes]

On 9/01/2018 4:35 AM, Jonathan Gibbons wrote:
Maybe the Makefile targets to run tests could report an up-front warning 
if the native libraries have not been built.


Based on my observations the makefile target will also build the 
test-image if needed.


David

A more advanced solution would be to use jtreg to determine if any 
native tests will be run (using some combination of `-k native` and 
`-listtests`) and if any such tests are found, then require the library 
to be available.


-- Jon

On 01/05/2018 06:37 PM, Alan Snyder wrote:
Following the instructions for the impatient, I did make images and 
then make run-test-tier1.
Then after replacing the jtreg with the one Jon recommended, I did 
make run-test-tier1 again.


   Alan


On Jan 5, 2018, at 6:32 PM, David Holmes  
wrote:


On 6/01/2018 12:05 PM, Alan Snyder wrote:

The tests were run via make.

How exactly? And did you do "make test-image" first?

David

On Jan 5, 2018, at 4:13 PM, David Holmes  
wrote:


Alan,

Unclear how you ran the tests, but:

TEST RESULT: Error. Use -nativepath to specify the location of 
native code


indicates jtreg was not passed the -nativepath flag. That may or 
may not be a build issue depending on whether the tests were 
executed directly or via "make".


Cheers,
David

On 6/01/2018 8:43 AM, Alan Snyder wrote:

5 test failures remain using jtreg-4.2.0-tip:
--
TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk 


ACTION: build -- Passed. Build successful
REASON: Named class compiled on demand
TIME: 1.179 seconds
messages:
command: build StringPlatformChars
reason: Named class compiled on demand
Test directory:
compile: StringPlatformChars
elapsed time (seconds): 1.179
ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME: 0.626 seconds
messages:
command: compile 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java 


reason: .class file out of date or does not exist
Mode: agentvm
Agent id: 1
elapsed time (seconds): 0.626
configuration:
Boot Layer (javac runtime environment)
class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
/Users/alan/javalib/share/jtreg/lib/jtreg.jar
patch: java.base 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base 


javac compilation environment
source path: 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
class path: 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d 


rerun:
cd 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0 
&& \

HOME=/Users/alan \
JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \
LANG=en_US.UTF-8 \
LC_ALL=en_US.UTF-8 \
PATH=/bin:/usr/bin \
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac 
\

-J-Xmx512m \
-J-XX:MaxRAMPercentage=3 \
-J-ea \
-J-esa \
-J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
\
-J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
\
-J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
\
-J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d 
\
-J-Dtest.class.path=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d 
\

-J-Dtest.vm.opts='-Xmx512m -XX:MaxRAMPercentage=3 -ea -esa' \
-J-Dtest.tool.vm.opts='-J-Xmx512m -J-XX:MaxRAMPercentage=3 -J-ea 
-J-esa' \

-J-Dtest.compiler.opts= \
-J-Dtest.java.opts= \
-J-Dtest.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk 
\
-J-Dcompile.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk 
\

-J-Dtest.timeout.factor=4.0 \
-d 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d 
\
-sourcepath 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \
-classpath 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding:/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/c

Re: jdk10 on macOS

[Jonathan Gibbons]

Maybe the Makefile targets to run tests could report an up-front warning 
if the native libraries have not been built.


A more advanced solution would be to use jtreg to determine if any 
native tests will be run (using some combination of `-k native` and 
`-listtests`) and if any such tests are found, then require the library 
to be available.


-- Jon

On 01/05/2018 06:37 PM, Alan Snyder wrote:

Following the instructions for the impatient, I did make images and then make 
run-test-tier1.
Then after replacing the jtreg with the one Jon recommended, I did make 
run-test-tier1 again.

   Alan



On Jan 5, 2018, at 6:32 PM, David Holmes  wrote:

On 6/01/2018 12:05 PM, Alan Snyder wrote:

The tests were run via make.

How exactly? And did you do "make test-image" first?

David


On Jan 5, 2018, at 4:13 PM, David Holmes  wrote:

Alan,

Unclear how you ran the tests, but:

TEST RESULT: Error. Use -nativepath to specify the location of native code

indicates jtreg was not passed the -nativepath flag. That may or may not be a build issue 
depending on whether the tests were executed directly or via "make".

Cheers,
David

On 6/01/2018 8:43 AM, Alan Snyder wrote:

5 test failures remain using jtreg-4.2.0-tip:
--
TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
ACTION: build -- Passed. Build successful
REASON: Named class compiled on demand
TIME: 1.179 seconds
messages:
command: build StringPlatformChars
reason: Named class compiled on demand
Test directory:
compile: StringPlatformChars
elapsed time (seconds): 1.179
ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME: 0.626 seconds
messages:
command: compile 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
reason: .class file out of date or does not exist
Mode: agentvm
Agent id: 1
elapsed time (seconds): 0.626
configuration:
Boot Layer (javac runtime environment)
class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
/Users/alan/javalib/share/jtreg/lib/jtreg.jar
patch: java.base 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base
javac compilation environment
source path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
class path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
rerun:
cd 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
 && \
HOME=/Users/alan \
JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \
LANG=en_US.UTF-8 \
LC_ALL=en_US.UTF-8 \
PATH=/bin:/usr/bin \
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
 \
-J-Xmx512m \
-J-XX:MaxRAMPercentage=3 \
-J-ea \
-J-esa \
-J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 \
-J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \
-J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
\
-J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \
-J-Dtest.class.path=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \
-J-Dtest.vm.opts='-Xmx512m -XX:MaxRAMPercentage=3 -ea -esa' \
-J-Dtest.tool.vm.opts='-J-Xmx512m -J-XX:MaxRAMPercentage=3 -J-ea -J-esa' \
-J-Dtest.compiler.opts= \
-J-Dtest.java.opts= \
-J-Dtest.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \
-J-Dcompile.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \
-J-Dtest.timeout.factor=4.0 \
-d 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \
-sourcepath /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \
-classpath 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding:/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
TEST RESULT: Error. 

Re: jdk10 on macOS

[Alan Snyder]

Following the instructions for the impatient, I did make images and then make 
run-test-tier1.
Then after replacing the jtreg with the one Jon recommended, I did make 
run-test-tier1 again.

  Alan


> On Jan 5, 2018, at 6:32 PM, David Holmes  wrote:
> 
> On 6/01/2018 12:05 PM, Alan Snyder wrote:
>> The tests were run via make.
> 
> How exactly? And did you do "make test-image" first?
> 
> David
> 
>>> On Jan 5, 2018, at 4:13 PM, David Holmes  wrote:
>>> 
>>> Alan,
>>> 
>>> Unclear how you ran the tests, but:
>>> 
>>> TEST RESULT: Error. Use -nativepath to specify the location of native code
>>> 
>>> indicates jtreg was not passed the -nativepath flag. That may or may not be 
>>> a build issue depending on whether the tests were executed directly or via 
>>> "make".
>>> 
>>> Cheers,
>>> David
>>> 
>>> On 6/01/2018 8:43 AM, Alan Snyder wrote:
 5 test failures remain using jtreg-4.2.0-tip:
 --
 TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
 TEST JDK: 
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 ACTION: build -- Passed. Build successful
 REASON: Named class compiled on demand
 TIME: 1.179 seconds
 messages:
 command: build StringPlatformChars
 reason: Named class compiled on demand
 Test directory:
 compile: StringPlatformChars
 elapsed time (seconds): 1.179
 ACTION: compile -- Passed. Compilation successful
 REASON: .class file out of date or does not exist
 TIME: 0.626 seconds
 messages:
 command: compile 
 /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
 reason: .class file out of date or does not exist
 Mode: agentvm
 Agent id: 1
 elapsed time (seconds): 0.626
 configuration:
 Boot Layer (javac runtime environment)
 class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
 /Users/alan/javalib/share/jtreg/lib/jtreg.jar
 patch: java.base 
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base
 javac compilation environment
 source path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 class path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 rerun:
 cd 
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
  && \
 HOME=/Users/alan \
 JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \
 LANG=en_US.UTF-8 \
 LC_ALL=en_US.UTF-8 \
 PATH=/bin:/usr/bin \
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
  \
 -J-Xmx512m \
 -J-XX:MaxRAMPercentage=3 \
 -J-ea \
 -J-esa \
 -J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
  \
 -J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
 \
 -J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
  \
 -J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
  \
 -J-Dtest.class.path=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
  \
 -J-Dtest.vm.opts='-Xmx512m -XX:MaxRAMPercentage=3 -ea -esa' \
 -J-Dtest.tool.vm.opts='-J-Xmx512m -J-XX:MaxRAMPercentage=3 -J-ea -J-esa' \
 -J-Dtest.compiler.opts= \
 -J-Dtest.java.opts= \
 -J-Dtest.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
  \
 -J-Dcompile.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
  \
 -J-Dtest.timeout.factor=4.0 \
 -d 
 /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
  \
 -sourcepath /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \
 -classpath 
 /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding:/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
  
 /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/na

Re: jdk10 on macOS

[David Holmes]

On 6/01/2018 12:05 PM, Alan Snyder wrote:

The tests were run via make.


How exactly? And did you do "make test-image" first?

David


On Jan 5, 2018, at 4:13 PM, David Holmes  wrote:

Alan,

Unclear how you ran the tests, but:

TEST RESULT: Error. Use -nativepath to specify the location of native code

indicates jtreg was not passed the -nativepath flag. That may or may not be a build issue 
depending on whether the tests were executed directly or via "make".

Cheers,
David

On 6/01/2018 8:43 AM, Alan Snyder wrote:

5 test failures remain using jtreg-4.2.0-tip:
--
TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
ACTION: build -- Passed. Build successful
REASON: Named class compiled on demand
TIME: 1.179 seconds
messages:
command: build StringPlatformChars
reason: Named class compiled on demand
Test directory:
compile: StringPlatformChars
elapsed time (seconds): 1.179
ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME: 0.626 seconds
messages:
command: compile 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
reason: .class file out of date or does not exist
Mode: agentvm
Agent id: 1
elapsed time (seconds): 0.626
configuration:
Boot Layer (javac runtime environment)
class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
/Users/alan/javalib/share/jtreg/lib/jtreg.jar
patch: java.base 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base
javac compilation environment
source path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
class path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
rerun:
cd 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
 && \
HOME=/Users/alan \
JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \
LANG=en_US.UTF-8 \
LC_ALL=en_US.UTF-8 \
PATH=/bin:/usr/bin \
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
 \
-J-Xmx512m \
-J-XX:MaxRAMPercentage=3 \
-J-ea \
-J-esa \
-J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 \
-J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \
-J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
\
-J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \
-J-Dtest.class.path=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \
-J-Dtest.vm.opts='-Xmx512m -XX:MaxRAMPercentage=3 -ea -esa' \
-J-Dtest.tool.vm.opts='-J-Xmx512m -J-XX:MaxRAMPercentage=3 -J-ea -J-esa' \
-J-Dtest.compiler.opts= \
-J-Dtest.java.opts= \
-J-Dtest.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \
-J-Dcompile.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \
-J-Dtest.timeout.factor=4.0 \
-d 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \
-sourcepath /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \
-classpath 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding:/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
TEST RESULT: Error. Use -nativepath to specify the location of native code
--
TEST: jdk/internal/misc/JavaLangAccess/NewUnsafeString.java
TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
ACTION: compile -- Passed. Compilation successful
REASON: User specified action: run compile -XDignore.symbol.file 
NewUnsafeString.java
TIME: 0.03 seconds
messages:
command: compile -XDignore.symbol.file 
/Volumes/A/JDK/jdk10/test/jdk/jdk/internal/misc/JavaLangAccess/NewUnsafeString.java
reason: User specified action: run compile -XDignore.symbol.file 
NewUnsafeString.java
Additional options from 

Re: jdk10 on macOS

[Alan Snyder]

The tests were run via make.

> On Jan 5, 2018, at 4:13 PM, David Holmes  wrote:
> 
> Alan,
> 
> Unclear how you ran the tests, but:
> 
> TEST RESULT: Error. Use -nativepath to specify the location of native code
> 
> indicates jtreg was not passed the -nativepath flag. That may or may not be a 
> build issue depending on whether the tests were executed directly or via 
> "make".
> 
> Cheers,
> David
> 
> On 6/01/2018 8:43 AM, Alan Snyder wrote:
>> 5 test failures remain using jtreg-4.2.0-tip:
>> --
>> TEST: java/lang/String/nativeEncoding/StringPlatformChars.java
>> TEST JDK: 
>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
>> ACTION: build -- Passed. Build successful
>> REASON: Named class compiled on demand
>> TIME: 1.179 seconds
>> messages:
>> command: build StringPlatformChars
>> reason: Named class compiled on demand
>> Test directory:
>> compile: StringPlatformChars
>> elapsed time (seconds): 1.179
>> ACTION: compile -- Passed. Compilation successful
>> REASON: .class file out of date or does not exist
>> TIME: 0.626 seconds
>> messages:
>> command: compile 
>> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
>> reason: .class file out of date or does not exist
>> Mode: agentvm
>> Agent id: 1
>> elapsed time (seconds): 0.626
>> configuration:
>> Boot Layer (javac runtime environment)
>> class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar
>> /Users/alan/javalib/share/jtreg/lib/jtreg.jar
>> patch: java.base 
>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base
>> javac compilation environment
>> source path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>> class path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
>> rerun:
>> cd 
>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
>>  && \
>> HOME=/Users/alan \
>> JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \
>> LANG=en_US.UTF-8 \
>> LC_ALL=en_US.UTF-8 \
>> PATH=/bin:/usr/bin \
>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
>>  \
>> -J-Xmx512m \
>> -J-XX:MaxRAMPercentage=3 \
>> -J-ea \
>> -J-esa \
>> -J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>>  \
>> -J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \
>> -J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
>>  \
>> -J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
>>  \
>> -J-Dtest.class.path=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
>>  \
>> -J-Dtest.vm.opts='-Xmx512m -XX:MaxRAMPercentage=3 -ea -esa' \
>> -J-Dtest.tool.vm.opts='-J-Xmx512m -J-XX:MaxRAMPercentage=3 -J-ea -J-esa' \
>> -J-Dtest.compiler.opts= \
>> -J-Dtest.java.opts= \
>> -J-Dtest.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
>>  \
>> -J-Dcompile.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
>>  \
>> -J-Dtest.timeout.factor=4.0 \
>> -d 
>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
>>  \
>> -sourcepath /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \
>> -classpath 
>> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding:/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
>>  
>> /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java
>> TEST RESULT: Error. Use -nativepath to specify the location of native code
>> --
>> TEST: jdk/internal/misc/JavaLangAccess/NewUnsafeString.java
>> TEST JDK: 
>> /Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
>> ACTION: compile -- Passed. Compilation successful
>> REASON: User specified action: run compile -XDignore.symbol.file 
>> NewUnsafeString.java
>> TIME: 0.03 seconds
>> messages:
>> command: compile -XDignore.symbol.file 
>> /Volumes/

Re: jdk10 on macOS

[David Holmes]

Also:

jdk/internal/misc/JavaLangAccess/NewUnsafeString

seems to be a JDK 9 test, I don't see it in the current sources:

http://hg.openjdk.java.net/jdk/jdk10/file/ccbf1c998dd9/test/jdk/jdk/internal/misc

David

On 6/01/2018 8:43 AM, Alan Snyder wrote:

5 test failures remain using jtreg-4.2.0-tip:

--

TEST: java/lang/String/nativeEncoding/StringPlatformChars.java

TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk

ACTION: build -- Passed. Build successful

REASON: Named class compiled on demand

TIME: 1.179 seconds

messages:

command: build StringPlatformChars

reason: Named class compiled on demand

Test directory:

compile: StringPlatformChars

elapsed time (seconds): 1.179

ACTION: compile -- Passed. Compilation successful

REASON: .class file out of date or does not exist

TIME: 0.626 seconds

messages:

command: compile 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java

reason: .class file out of date or does not exist

Mode: agentvm

Agent id: 1

elapsed time (seconds): 0.626

configuration:

Boot Layer (javac runtime environment)

class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar

/Users/alan/javalib/share/jtreg/lib/jtreg.jar

patch: java.base 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base

javac compilation environment

source path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding

class path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding

/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d

rerun:

cd 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
 && \

HOME=/Users/alan \

JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \

LANG=en_US.UTF-8 \

LC_ALL=en_US.UTF-8 \

PATH=/bin:/usr/bin \

/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
 \

-J-Xmx512m \

-J-XX:MaxRAMPercentage=3 \

-J-ea \

-J-esa \

-J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 \

-J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \

-J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
\

-J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-J-Dtest.class.path=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-J-Dtest.vm.opts='-Xmx512m -XX:MaxRAMPercentage=3 -ea -esa' \

-J-Dtest.tool.vm.opts='-J-Xmx512m -J-XX:MaxRAMPercentage=3 -J-ea -J-esa' \

-J-Dtest.compiler.opts= \

-J-Dtest.java.opts= \

-J-Dtest.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \

-J-Dcompile.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \

-J-Dtest.timeout.factor=4.0 \

-d 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-sourcepath /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \

-classpath 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding:/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java

TEST RESULT: Error. Use -nativepath to specify the location of native code

--

TEST: jdk/internal/misc/JavaLangAccess/NewUnsafeString.java

TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk

ACTION: compile -- Passed. Compilation successful

REASON: User specified action: run compile -XDignore.symbol.file 
NewUnsafeString.java

TIME: 0.03 seconds

messages:

command: compile -XDignore.symbol.file 
/Volumes/A/JDK/jdk10/test/jdk/jdk/internal/misc/JavaLangAccess/NewUnsafeString.java

reason: User specified action: run compile -XDignore.symbol.file 
NewUnsafeString.java

Additional options from @modules: --add-modules java.base --add-exports 
java.base/jdk.internal.misc=ALL-UNNAMED

Mode: agentvm

Agent id: 1

elapsed time (seconds): 0.03

configuration:

Boot Layer (javac runtime environment

Re: jdk10 on macOS

[David Holmes]

Alan,

Unclear how you ran the tests, but:

TEST RESULT: Error. Use -nativepath to specify the location of native code

indicates jtreg was not passed the -nativepath flag. That may or may not 
be a build issue depending on whether the tests were executed directly 
or via "make".


Cheers,
David

On 6/01/2018 8:43 AM, Alan Snyder wrote:

5 test failures remain using jtreg-4.2.0-tip:

--

TEST: java/lang/String/nativeEncoding/StringPlatformChars.java

TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk

ACTION: build -- Passed. Build successful

REASON: Named class compiled on demand

TIME: 1.179 seconds

messages:

command: build StringPlatformChars

reason: Named class compiled on demand

Test directory:

compile: StringPlatformChars

elapsed time (seconds): 1.179

ACTION: compile -- Passed. Compilation successful

REASON: .class file out of date or does not exist

TIME: 0.626 seconds

messages:

command: compile 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java

reason: .class file out of date or does not exist

Mode: agentvm

Agent id: 1

elapsed time (seconds): 0.626

configuration:

Boot Layer (javac runtime environment)

class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar

/Users/alan/javalib/share/jtreg/lib/jtreg.jar

patch: java.base 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base

javac compilation environment

source path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding

class path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding

/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d

rerun:

cd 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
 && \

HOME=/Users/alan \

JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \

LANG=en_US.UTF-8 \

LC_ALL=en_US.UTF-8 \

PATH=/bin:/usr/bin \

/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
 \

-J-Xmx512m \

-J-XX:MaxRAMPercentage=3 \

-J-ea \

-J-esa \

-J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 \

-J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \

-J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
\

-J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-J-Dtest.class.path=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-J-Dtest.vm.opts='-Xmx512m -XX:MaxRAMPercentage=3 -ea -esa' \

-J-Dtest.tool.vm.opts='-J-Xmx512m -J-XX:MaxRAMPercentage=3 -J-ea -J-esa' \

-J-Dtest.compiler.opts= \

-J-Dtest.java.opts= \

-J-Dtest.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \

-J-Dcompile.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \

-J-Dtest.timeout.factor=4.0 \

-d 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-sourcepath /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \

-classpath 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding:/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java

TEST RESULT: Error. Use -nativepath to specify the location of native code

--

TEST: jdk/internal/misc/JavaLangAccess/NewUnsafeString.java

TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk

ACTION: compile -- Passed. Compilation successful

REASON: User specified action: run compile -XDignore.symbol.file 
NewUnsafeString.java

TIME: 0.03 seconds

messages:

command: compile -XDignore.symbol.file 
/Volumes/A/JDK/jdk10/test/jdk/jdk/internal/misc/JavaLangAccess/NewUnsafeString.java

reason: User specified action: run compile -XDignore.symbol.file 
NewUnsafeString.java

Additional options from @modules: --add-modules java.base --add-exports 
java.base/jdk.internal.misc=ALL-UNNAMED

Mode: agentvm

Agent id: 1

Re: jdk10 on macOS

[Alan Snyder]

5 test failures remain using jtreg-4.2.0-tip:

--

TEST: java/lang/String/nativeEncoding/StringPlatformChars.java

TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk

ACTION: build -- Passed. Build successful

REASON: Named class compiled on demand

TIME: 1.179 seconds

messages:

command: build StringPlatformChars

reason: Named class compiled on demand

Test directory:

compile: StringPlatformChars

elapsed time (seconds): 1.179

ACTION: compile -- Passed. Compilation successful

REASON: .class file out of date or does not exist

TIME: 0.626 seconds

messages:

command: compile 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java

reason: .class file out of date or does not exist

Mode: agentvm

Agent id: 1

elapsed time (seconds): 0.626

configuration:

Boot Layer (javac runtime environment)

class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar

/Users/alan/javalib/share/jtreg/lib/jtreg.jar

patch: java.base 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/java.base

javac compilation environment

source path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding

class path: /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding

/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d

rerun:

cd 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/scratch/0
 && \

HOME=/Users/alan \

JDK8_HOME=/Library/Java/JavaVirtualMachines/1.9.0.jdk/Contents/Home \

LANG=en_US.UTF-8 \

LC_ALL=en_US.UTF-8 \

PATH=/bin:/usr/bin \

/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk/bin/javac
 \

-J-Xmx512m \

-J-XX:MaxRAMPercentage=3 \

-J-ea \

-J-esa \

-J-Dtest.class.path.prefix=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d:/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding
 \

-J-Dtest.src=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \

-J-Dtest.src.path=/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding 
\

-J-Dtest.classes=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-J-Dtest.class.path=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-J-Dtest.vm.opts='-Xmx512m -XX:MaxRAMPercentage=3 -ea -esa' \

-J-Dtest.tool.vm.opts='-J-Xmx512m -J-XX:MaxRAMPercentage=3 -J-ea -J-esa' \

-J-Dtest.compiler.opts= \

-J-Dtest.java.opts= \

-J-Dtest.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \

-J-Dcompile.jdk=/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk
 \

-J-Dtest.timeout.factor=4.0 \

-d 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 \

-sourcepath /Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding \

-classpath 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding:/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/classes/4/java/lang/String/nativeEncoding/StringPlatformChars.d
 
/Volumes/A/JDK/jdk10/test/jdk/java/lang/String/nativeEncoding/StringPlatformChars.java

TEST RESULT: Error. Use -nativepath to specify the location of native code

--

TEST: jdk/internal/misc/JavaLangAccess/NewUnsafeString.java

TEST JDK: 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/images/jdk

ACTION: compile -- Passed. Compilation successful

REASON: User specified action: run compile -XDignore.symbol.file 
NewUnsafeString.java

TIME: 0.03 seconds

messages:

command: compile -XDignore.symbol.file 
/Volumes/A/JDK/jdk10/test/jdk/jdk/internal/misc/JavaLangAccess/NewUnsafeString.java

reason: User specified action: run compile -XDignore.symbol.file 
NewUnsafeString.java

Additional options from @modules: --add-modules java.base --add-exports 
java.base/jdk.internal.misc=ALL-UNNAMED

Mode: agentvm

Agent id: 1

elapsed time (seconds): 0.03

configuration:

Boot Layer (javac runtime environment)

class path: /Users/alan/javalib/share/jtreg/lib/javatest.jar

/Users/alan/javalib/share/jtreg/lib/jtreg.jar

patch: java.base 
/Volumes/A/JDK/jdk10/build/macosx-x86_64-normal-server-release/test-support/jtreg_Volumes_A_JDK_jdk10_test_jdk_tier1/patches/j

Re: jdk10 on macOS

[Alan Snyder]

I am trying jtreg-4.2.0-tip now.

Building jtreg using build-all.sh made some progress until:

2018-01-05 14:02:03 (5.89 MB/s) - 
'/Volumes/A/JDK/jtreg/build/deps/ant/ant-1.7.0.jar' saved [1289806/1289806]

/Volumes/A/JDK/jtreg/build/deps/ant/ant-1.7.0.jar: OK
make: *** No rule to make target `391:a13ec77e7adc'.  Stop.

Also, the README must be out of date, because it does not mention build-all.sh.

  Alan


> On Jan 5, 2018, at 1:45 PM, Jonathan Gibbons  
> wrote:
> 
> 1. The build labelled jtreg-4.2.0-tip.tar.gz should work for you.
> https://ci.adoptopenjdk.net/view/Dependencies/job/jtreg/ 
> 
> 
> 2. The build instructions are here:
> http://openjdk.java.net/jtreg/build.html 
> 
> See the section on using the "build-all.sh" script.
> 
> -- Jon
> 
> On 01/05/2018 01:35 PM, Alan Snyder wrote:
>> Maybe not as easy as you expect:
>> 
>> ant -f make/build.xml
>> Buildfile: /Volumes/A/JDK/jtreg/make/build.xml
>> 
>> -init:
>> 
>> import-javahelp:
>> 
>> BUILD FAILED
>> /Volumes/A/JDK/jtreg/make/build.xml:246: Warning: Could not find file 
>> /opt/javahelp/2.0/javahelp/lib/jh.jar to copy.
>> 
>> 
>> 
>> make -C make
>> 
>> …
>> 
>> ../src/share/classes/com/sun/javatest/regtest/agent/TestNGRunner.java:33: 
>> error: package org.testng does not exist
>> 
>> ...
>> 
>> 
>>> On Jan 5, 2018, at 1:02 PM, Jonathan Gibbons >> > wrote:
>>> 
>>> Alan,
>>> 
>>> I confirm there are problems with the jtreg builds from the Adopt OpenJDK 
>>> group. I'll investigate what we can do to fix this.
>>> 
>>> -- Jon
>>> 
>>> On 01/05/2018 12:36 PM, Jonathan Gibbons wrote:
 That sounds like a problem using an older build of jtreg, from the Adopt 
 OpenJDK group. The tell-tale evidence is the Class-Path entry in the 
 jtreg.jar MANIFEST.MF file:  does that entry include asmtools.jar?
 
 There have been build changes for jtreg recently, that should have 
 addressed this problem. If nothing else, it is now much easier to build 
 jtreg yourself. The only external components you need are Ant and a recent 
 JDK, such as JDK 8. Everything else will be downloaded, and built if 
 necessary.
 
 -- Jon
 
 
 On 1/5/18 12:21 PM, Alan Snyder wrote:
> I am trying to build jdk10 on macOS 10.12.6. I got the basic build to 
> work, but some tests fail.
> 
> Most of the test failures complain about not finding jasm or jcoder. This 
> is odd because I downloaded jtreg-4.2-b11, which includes these classes, 
> and the classpath appears to be correct in the log.
> 
> I got an error from StringPlatformChars, which could find native code. 
> Could be the same jasm problem but not reported as such.
> 
> I got an error from NewUnsafeString, did not use provided string.
> 
 
>>> 
>> 
> 

Re: jdk10 on macOS

[Jonathan Gibbons]

1. The build labelled jtreg-4.2.0-tip.tar.gz should work for you.
https://ci.adoptopenjdk.net/view/Dependencies/job/jtreg/

2. The build instructions are here:
http://openjdk.java.net/jtreg/build.html
See the section on using the "build-all.sh" script.

-- Jon

On 01/05/2018 01:35 PM, Alan Snyder wrote:

Maybe not as easy as you expect:

ant -f make/build.xml
Buildfile: /Volumes/A/JDK/jtreg/make/build.xml

-init:

import-javahelp:

BUILD FAILED
/Volumes/A/JDK/jtreg/make/build.xml:246: Warning: Could not find file 
/opt/javahelp/2.0/javahelp/lib/jh.jar to copy.




make -C make

…

../src/share/classes/com/sun/javatest/regtest/agent/TestNGRunner.java:33: 
error: package org.testng does not exist


...


On Jan 5, 2018, at 1:02 PM, Jonathan Gibbons 
mailto:jonathan.gibb...@oracle.com>> wrote:


Alan,

I confirm there are problems with the jtreg builds from the Adopt 
OpenJDK group. I'll investigate what we can do to fix this.


-- Jon

On 01/05/2018 12:36 PM, Jonathan Gibbons wrote:
That sounds like a problem using an older build of jtreg, from the 
Adopt OpenJDK group. The tell-tale evidence is the Class-Path entry 
in the jtreg.jar MANIFEST.MF file:  does that entry include 
asmtools.jar?


There have been build changes for jtreg recently, that should have 
addressed this problem. If nothing else, it is now much easier to 
build jtreg yourself. The only external components you need are Ant 
and a recent JDK, such as JDK 8. Everything else will be downloaded, 
and built if necessary.


-- Jon


On 1/5/18 12:21 PM, Alan Snyder wrote:
I am trying to build jdk10 on macOS 10.12.6. I got the basic build 
to work, but some tests fail.


Most of the test failures complain about not finding jasm or 
jcoder. This is odd because I downloaded jtreg-4.2-b11, which 
includes these classes, and the classpath appears to be correct in 
the log.


I got an error from StringPlatformChars, which could find native 
code. Could be the same jasm problem but not reported as such.


I got an error from NewUnsafeString, did not use provided string.

Re: jdk10 on macOS

[Alan Snyder]

Maybe not as easy as you expect:

ant -f make/build.xml
Buildfile: /Volumes/A/JDK/jtreg/make/build.xml

-init:

import-javahelp:

BUILD FAILED
/Volumes/A/JDK/jtreg/make/build.xml:246: Warning: Could not find file 
/opt/javahelp/2.0/javahelp/lib/jh.jar to copy.



make -C make

…

../src/share/classes/com/sun/javatest/regtest/agent/TestNGRunner.java:33: 
error: package org.testng does not exist

...


> On Jan 5, 2018, at 1:02 PM, Jonathan Gibbons  
> wrote:
> 
> Alan,
> 
> I confirm there are problems with the jtreg builds from the Adopt OpenJDK 
> group. I'll investigate what we can do to fix this.
> 
> -- Jon
> 
> On 01/05/2018 12:36 PM, Jonathan Gibbons wrote:
>> That sounds like a problem using an older build of jtreg, from the Adopt 
>> OpenJDK group. The tell-tale evidence is the Class-Path entry in the 
>> jtreg.jar MANIFEST.MF file:  does that entry include asmtools.jar?
>> 
>> There have been build changes for jtreg recently, that should have addressed 
>> this problem. If nothing else, it is now much easier to build jtreg 
>> yourself. The only external components you need are Ant and a recent JDK, 
>> such as JDK 8. Everything else will be downloaded, and built if necessary.
>> 
>> -- Jon
>> 
>> 
>> On 1/5/18 12:21 PM, Alan Snyder wrote:
>>> I am trying to build jdk10 on macOS 10.12.6. I got the basic build to work, 
>>> but some tests fail.
>>> 
>>> Most of the test failures complain about not finding jasm or jcoder. This 
>>> is odd because I downloaded jtreg-4.2-b11, which includes these classes, 
>>> and the classpath appears to be correct in the log.
>>> 
>>> I got an error from StringPlatformChars, which could find native code. 
>>> Could be the same jasm problem but not reported as such.
>>> 
>>> I got an error from NewUnsafeString, did not use provided string.
>>> 
>> 
> 

Re: jdk10 on macOS

[Jonathan Gibbons]

Alan,

I confirm there are problems with the jtreg builds from the Adopt 
OpenJDK group. I'll investigate what we can do to fix this.


-- Jon

On 01/05/2018 12:36 PM, Jonathan Gibbons wrote:
That sounds like a problem using an older build of jtreg, from the 
Adopt OpenJDK group. The tell-tale evidence is the Class-Path entry in 
the jtreg.jar MANIFEST.MF file:  does that entry include asmtools.jar?


There have been build changes for jtreg recently, that should have 
addressed this problem. If nothing else, it is now much easier to 
build jtreg yourself. The only external components you need are Ant 
and a recent JDK, such as JDK 8. Everything else will be downloaded, 
and built if necessary.


-- Jon


On 1/5/18 12:21 PM, Alan Snyder wrote:
I am trying to build jdk10 on macOS 10.12.6. I got the basic build to 
work, but some tests fail.


Most of the test failures complain about not finding jasm or jcoder. 
This is odd because I downloaded jtreg-4.2-b11, which includes these 
classes, and the classpath appears to be correct in the log.


I got an error from StringPlatformChars, which could find native 
code. Could be the same jasm problem but not reported as such.


I got an error from NewUnsafeString, did not use provided string.

Re: jdk10 on macOS

[Jonathan Gibbons]

That sounds like a problem using an older build of jtreg, from the Adopt 
OpenJDK group. The tell-tale evidence is the Class-Path entry in the 
jtreg.jar MANIFEST.MF file:  does that entry include asmtools.jar?


There have been build changes for jtreg recently, that should have 
addressed this problem. If nothing else, it is now much easier to build 
jtreg yourself. The only external components you need are Ant and a 
recent JDK, such as JDK 8. Everything else will be downloaded, and built 
if necessary.


-- Jon


On 1/5/18 12:21 PM, Alan Snyder wrote:

I am trying to build jdk10 on macOS 10.12.6. I got the basic build to work, but 
some tests fail.

Most of the test failures complain about not finding jasm or jcoder. This is 
odd because I downloaded jtreg-4.2-b11, which includes these classes, and the 
classpath appears to be correct in the log.

I got an error from StringPlatformChars, which could find native code. Could be 
the same jasm problem but not reported as such.

I got an error from NewUnsafeString, did not use provided string.