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

Delete gradle-daemon-logs after testexecution #196

Open
mawHBT opened this issue Oct 11, 2022 · 3 comments
Open

Delete gradle-daemon-logs after testexecution #196

mawHBT opened this issue Oct 11, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@mawHBT
Copy link
Collaborator

mawHBT commented Oct 11, 2022

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

@mawHBT mawHBT added the enhancement New feature or request label Oct 11, 2022
@DaGeRe
Copy link
Contributor

DaGeRe commented Oct 11, 2022

Thanks for the issue. This should be fixed by DaGeRe/peass@5c876c2 - can you confirm this?

@DaGeRe DaGeRe self-assigned this Oct 11, 2022
@mawHBT
Copy link
Collaborator Author

mawHBT commented Oct 19, 2022

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?

@DaGeRe
Copy link
Contributor

DaGeRe commented Oct 19, 2022

Thanks for the update.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants