You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the Gradle daemon crashes, it would be great if the Gradle client would print the filepath of the hs_pid_file generated by the Gradle daemon (assuming that that file exists).
It would also be nice to print the first ~80 lines of that file too.
Current Behavior
Currently when the Gradle daemon crashes, the Gradle client doesn't mention the existence of an hs_err_pid file to the user.
Context
The AndroidX team has been observing our Gradle daemon to be crashing itermittently : http://issuetracker.google.com/issues/146217083 . Because our crashes occur nearly exclusively on continuous integration servers, we don't see the hs_err_pid files when they are generated (they're created in the working directory from which Gradle was executed, which is a directory that we otherwise wouldn't need to inspect).
If Gradle would display the filepath of the hs_err_pid file, it would be easier for developers to think to look for it and to make sure that the builder copies it into a location where it will be visible after the build completes.
Thanks
The text was updated successfully, but these errors were encountered:
Expected Behavior
When the Gradle daemon crashes, it would be great if the Gradle client would print the filepath of the hs_pid_file generated by the Gradle daemon (assuming that that file exists).
It would also be nice to print the first ~80 lines of that file too.
Current Behavior
Currently when the Gradle daemon crashes, the Gradle client doesn't mention the existence of an hs_err_pid file to the user.
Context
The AndroidX team has been observing our Gradle daemon to be crashing itermittently : http://issuetracker.google.com/issues/146217083 . Because our crashes occur nearly exclusively on continuous integration servers, we don't see the hs_err_pid files when they are generated (they're created in the working directory from which Gradle was executed, which is a directory that we otherwise wouldn't need to inspect).
However, we found it was super useful to inspect the hs_err_pid file: http://issuetracker.google.com/issues/146217083#comment39 .
If Gradle would display the filepath of the hs_err_pid file, it would be easier for developers to think to look for it and to make sure that the builder copies it into a location where it will be visible after the build completes.
Thanks
The text was updated successfully, but these errors were encountered: