Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed tests delete diagnostic (core/trace/javacore) files (or moved to an unknown location) #5454

Closed
JasonFengJ9 opened this issue Apr 11, 2019 · 2 comments · Fixed by adoptium/aqa-tests#1073

Comments

@JasonFengJ9
Copy link
Member

Summary of problem

As mentioned at #5399 (comment), in this particular test OpenJDK Regression suite jdk_util, the diagnostic files such as system core, snap trace and javacore disappeared from the location specified within console output.

Applying Ctrl-C to stop the test could make the diagnostic files available. So the diagnostic files were generated but were deleted quickly (or moved to an un-specific location).

fyi @smlambert

@smlambert
Copy link
Contributor

Thanks @JasonFengJ9 - yes, we have learned we need to use the --retain command line option with the underlying openjdk/jtreg framework in order to not have the framework quickly delete these files from the scratch folder. We are updating the WIP PR that will capture contents of scratch folder to accommodate this.

@llxia
Copy link
Contributor

llxia commented Apr 11, 2019

@smlambert and @JasonFengJ9 you are both correct.

From my local testing, the files got moved out of scratch folder even with -retain:fail,error,*.dmp,javacore.*,*.trc,*.phd.

Output:

[2019-04-11 14:13:48,293] Agent[8]: stderr: JVMDUMP032I JVM requested System dump using '/Users/lanxia/tmp/test/jvmtest/openjdk_regression/work/scratch/5/core.20190411.141348.43289.0001.dmp' in response to an event
[2019-04-11 14:13:52,013] Agent[8]: stderr: JVMDUMP010I System dump written to /Users/lanxia/tmp/test/jvmtest/openjdk_regression/work/scratch/5/core.20190411.141348.43289.0001.dmp
[2019-04-11 14:13:52,014] Agent[8]: stderr: JVMDUMP032I JVM requested Java dump using '/Users/lanxia/tmp/test/jvmtest/openjdk_regression/work/scratch/5/javacore.20190411.141348.43289.0002.txt' in response to an event
[2019-04-11 14:13:52,334] Agent[8]: stderr: JVMDUMP010I Java dump written to /Users/lanxia/tmp/test/jvmtest/openjdk_regression/work/scratch/5/javacore.20190411.141348.43289.0002.txt
[2019-04-11 14:13:52,334] Agent[8]: stderr: JVMDUMP032I JVM requested Snap dump using '/Users/lanxia/tmp/test/jvmtest/openjdk_regression/work/scratch/5/Snap.20190411.141348.43289.0003.trc' in response to an event
[2019-04-11 14:13:52,443] Agent[8]: stderr: JVMDUMP010I Snap dump written to /Users/lanxia/tmp/test/jvmtest/openjdk_regression/work/scratch/5/Snap.20190411.141348.43289.0003.trc

system core, snap trace and javacore are actually located at work/java/...

Lans-MacBook-Pro:openjdk_regression lanxia$ find . -name *.dmp
./work/java/util/jar/JarFile/mrjar/MultiReleaseJarHttpProperties/core.20190411.141348.43289.0001.dmp
./work/java/util/ResourceBundle/Bug4168625Test/core.20190411.141630.43279.0001.dmp

I will create a PR soon to point workDir to TKG reportDir and update -retain cmd, so that diagnostic files are archived.

Reference links:
https://openjdk.java.net/jtreg/command-help.html
https://openjdk.java.net/jtreg/faq.html#scratch-directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants