-
Notifications
You must be signed in to change notification settings - Fork 728
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
Comments
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. |
@smlambert and @JasonFengJ9 you are both correct. From my local testing, the files got moved out of Output:
system core, snap trace and javacore are actually located at
I will create a PR soon to point workDir to TKG reportDir and update Reference links: |
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
The text was updated successfully, but these errors were encountered: