Hi.
Could you please take a look on the fix:
http://cr.openjdk.java.net/~shurailine/8156972/webrev.00/
Besides adding @modules, I have also added a couple of lines to the library
class, because I have found the NPE which I was getting originally
non-informative.
Shura
On 13/05/2016 20:29, Martin Buchholz wrote:
:
Thanks! That explains why I can still run jtreg -agentvm on openjdk itself.
(But useNewXpatch feels wrong because it's not a property of the test
suite itself, but of the testjdk ...)
I agree but it was just for transition purposes to keep existing
> On May 13, 2016, at 1:20 AM, Sundararajan Athijegannathan
> wrote:
>
> Please review http://cr.openjdk.java.net/~sundar/8156914/webrev.00/ for
> https://bugs.openjdk.java.net/browse/JDK-8156914
>
This patch looks okay. The renamed
On Fri, May 13, 2016 at 12:18 PM, Alan Bateman wrote:
> On 13/05/2016 20:04, Martin Buchholz wrote:
>>
>> I tried updating jsr166 to jdk-9+118 today, but there's a snag - jtreg
>> won't start.
>> A simple repro is:
>>
>> jtreg -agentvm
On 13/05/2016 20:04, Martin Buchholz wrote:
I tried updating jsr166 to jdk-9+118 today, but there's a snag - jtreg
won't start.
A simple repro is:
jtreg -agentvm -testjdk:/home/martin/jdk/jdk-9-ea+118 .
Agent[0].stdout: Bad value for -Xpatch, no module name specified
Agent[0].stderr: Error:
I tried updating jsr166 to jdk-9+118 today, but there's a snag - jtreg
won't start.
A simple repro is:
jtreg -agentvm -testjdk:/home/martin/jdk/jdk-9-ea+118 .
Agent[0].stdout: Bad value for -Xpatch, no module name specified
Agent[0].stderr: Error: Could not create the Java Virtual Machine.
Please review http://cr.openjdk.java.net/~sundar/8156914/webrev.00/ for
https://bugs.openjdk.java.net/browse/JDK-8156914
Thanks,
-Sundar