Other |
---|
tbdResolved |
Relates :
|
|
Relates :
|
The following test timed out in the JDK18 CI: vmTestbase/nsk/jvmti/RedefineClasses/StressRedefine/TestDescription.java Here's a snippet from the log file: <<<<<<<< RedefineClasses() is successfully done t:\\workspace\\open\\test\\hotspot\\jtreg\\vmTestbase\\nsk\\jvmti\\RedefineClasses\\StressRedefine\\stressRedefine.cpp: Failed to call RedefineClasses(): the function returned error 60: JVMTI_ERROR_INVALID_CLASS_FORMAT For more info about this error see the JVMTI spec. >>>>>>>> Invoke RedefineClasses(): new class byte count=2283 >>>>>>>> Invoke RedefineClasses(): new class byte count=2283 <<<<<<<< RedefineClasses() is successfully done >>>>>>>> Invoke RedefineClasses(): new class byte count=2283 <<<<<<<< RedefineClasses() is successfully done >>>>>>>> Invoke RedefineClasses(): new class byte count=2283 <<<<<<<< RedefineClasses() is successfully done Timeout refired 1200 times >>>>>>>> ----------System.err:(0/0)---------- ----------rerun:(41/6545)*---------- < snip> result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-18+16-901\windows-x64-debug.jdk\jdk-18\fastdebug\bin\java' timed out (timeout set to 1200000ms, elapsed time including timeout handling was 1327406ms). Please note there are quite a few exception thrown and RedefineClasses failures reported in the log file. Those failure modes appear to be intentional. The failure mode being tracked by this bug is a time out.