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
In .gradle/daemon/$GRADLE_VERSION many log-files (daemon-XXX.out.log) are created. These are sometimes extremely big and fill up our HDD in short time.
These files should be deleted, directly after testexecution.
Upstream changes
No response
The text was updated successfully, but these errors were encountered:
Sometimes you must search in more lines for the pid of the daemon-logfile needed for deletion. This PR fixes this.
But some logs still remained, so I deleted them all and executed a job with: cleanPerformanceMeasurement cleanRTS: false
Measurements took place, no significant changes where detected, so no RCA was executed. Therefore, remaining logs must have been created while measurement, right?
From my point of view, it is rather unlikely that gradle daemon log files are created during the measurement (since it contains of much less complicated operations than the rts or the rca). I'd rather assume that another process created the daemon logs.
But to debug this, you can have a look at the individual measurement logs and look where their daemon-logfile is created - if this is in the measurement log, please post the relevant part of the log file here, so we can have a look at this.
What feature do you want to see added?
In .gradle/daemon/$GRADLE_VERSION many log-files (daemon-XXX.out.log) are created. These are sometimes extremely big and fill up our HDD in short time.
These files should be deleted, directly after testexecution.
Upstream changes
No response
The text was updated successfully, but these errors were encountered: