|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I still don't see a bug here. After a build is finished, the same thread performs the log rotation. The build log file is not yet closed, and there's a progress indicator. If there are many files to delete, it will take some time to finish. If Jenkins needs to traverse a complex build graph to determine what can be deleted, that will also take time. This just is how it works, and not a bug. At this point in time, the build is considered finished, and the build result is final.
Or am I missing something here?