RFR: 8233784: ProblemList failing JVMTI scenario tests

[David Holmes]

Hi Goetz,

Thanks for looking at this.

On 7/11/2019 9:39 pm, Lindenmaier, Goetz wrote:
> Hi David,
> 
> we also see these failures in our CI. It is intermittent and on all platforms.
> It happens since Nov 4.
> 
> We saw the following ones you already listed:
>    vmTestbase/nsk/jvmti/scenarios/allocation/AP12/ap12t001/TestDescription.java
>    vmTestbase/nsk/jvmti/scenarios/events/EM02/em02t005/TestDescription.java
> 
> Further we saw this one, could you please add it, too?
>    vmTestbase/nsk/jvmti/scenarios/events/EM07/em07t002/TestDescription.java
> It failed once with the same kind of message.

My latest test run just saw that one fail too.

> Besides that, the change looks good.
> 
> Further we saw these failing, but I'm not sure it's the same issue:
>    vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t001/TestDescription.java
>    vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t002/TestDescription.java
> with this message:

Yes this is the same issue. I've ensured both are in the list.

I now have 11 on the list, which leaves 151 that have not yet been seen 
to fail. Any test that uses the AgentThread functionality and uses a 
RawMonitorWait is potentially affected. Unfortunately there seems to be 
no easy way to actually determine all the tests affected due to the use 
of utility functions.

I'll push what I have now so that we can stem the failures. 
Unfortunately I'm out of the office tomorrow morning.

Thanks,
David
-----

> CASE #3:
> Allocating objects...
> Start heap iteration thread and field modification loop
> thread3 started.
> - ap04t002.cpp, 346: Calling IterateOverObjectsReachableFromObject...
> - ap04t002.cpp, 352: IterateOverObjectsReachableFromObject finished.
> - ap04t002.cpp, 354: Iterations count: 247089
> - ap04t002.cpp, 355: Modifications count: 14
> - ap04t002.cpp, 358: Errors detected: 0
> Wait for completion thread to finish
> thread3 finished.
> Cleaning tags and references to objects...
> The following fake exception stacktrace is for failure analysis.
> nsk.share.Fake_Exception_for_RULE_Creation: (jvmti_tools.cpp:683) error
> 	at nsk_lvcomplain(nsk_tools.cpp:172)
> # ERROR: jvmti_tools.cpp, 683: error
> #   jvmti error: code=52, name=JVMTI_ERROR_INTERRUPT
> CASE #3 finished.
> 
> CASE #4:
> Allocating objects...
> ----------System.err:(18/4306)----------
> java.lang.AssertionError: .../jvm_14/bin/java, -Xmx768m, -Djava.awt.headless=true,  ... -agentlib:ap04t002=-waittime=5 -verbose, nsk.jvmti.scenarios.allocation.AP04.ap04t002] exit code is 52
> 	at ExecDriver.main(ExecDriver.java:137)
> 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 	at PropertyResolvingWrapper.main(PropertyResolvingWrapper.java:104)
> 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
> 	at java.base/java.lang.Thread.run(Thread.java:833)
> 
> 
>> -----Original Message-----
>> From: hotspot-runtime-dev <hotspot-runtime-dev-bounces at openjdk.java.net>
>> On Behalf Of David Holmes
>> Sent: Donnerstag, 7. November 2019 11:45
>> To: serviceability-dev <serviceability-dev at openjdk.java.net>; hotspot-runtime-
>> dev at openjdk.java.net
>> Subject: RFR: 8233784: ProblemList failing JVMTI scenario tests
>>
>> Bug: https://bugs.openjdk.java.net/browse/JDK-8233784
>>
>> Patch below.
>>
>> Getting the fix tested will take a little while and we are getting
>> numerous failures in our CI testing. I ran all the scenario tests
>> multiple times to try and find all that fail due to this problem. It may
>> not be exhaustive, so if needed I'll add more later.
>>
>> Thanks,
>> David
>> -----
>>
>> iff -r bb2a436e616c test/hotspot/jtreg/ProblemList.txt
>> --- a/test/hotspot/jtreg/ProblemList.txt
>> +++ b/test/hotspot/jtreg/ProblemList.txt
>> @@ -206,4 +206,14 @@
>>
>>
>> vmTestbase/nsk/jdwp/ThreadReference/ForceEarlyReturn/forceEarlyReturn00
>> 1/forceEarlyReturn001.java
>> 7199837 generic-all
>>
>> -
>> ##################################################################
>> ###########
>> +vmTestbase/nsk/jvmti/scenarios/allocation/AP01/ap01t001/TestDescription.
>> java
>> 8233549 generic-all
>> +vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t002/TestDescription.
>> java
>> 8233549 generic-all
>> +vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t003/TestDescription.
>> java
>> 8233549 generic-all
>> +vmTestbase/nsk/jvmti/scenarios/allocation/AP12/ap12t001/TestDescription.
>> java
>> 8233549 generic-all
>> +vmTestbase/nsk/jvmti/scenarios/capability/CM02/cm02t001/TestDescriptio
>> n.java
>> 8233549 generic-all
>> +vmTestbase/nsk/jvmti/scenarios/events/EM02/em02t002/TestDescription.ja
>> va
>> 8233549 generic-all
>> +vmTestbase/nsk/jvmti/scenarios/events/EM02/em02t003/TestDescription.ja
>> va
>> 8233549 generic-all
>> +vmTestbase/nsk/jvmti/scenarios/events/EM02/em02t005/TestDescription.ja
>> va
>> 8233549 generic-all
>> +vmTestbase/nsk/jvmti/scenarios/events/EM02/em02t006/TestDescription.ja
>> va
>> 8233549 generic-all
>> +
>> +#################################################################
>> ############