|
||||||||
|
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.
Would be interesting which logs you have installed, how the job is configured (e.g. parallel execution), when this issue occurred and when the "original" build 96 was created.
Could you install the Support Core plugin and attach a support bundle to this issue?
There are a few issues related to that (JENKINS-26582 is at least similar) since 1.597 changed how builds are stored on disk, but we don't yet have the cause. And the alternative to just overwrite the original build's data is even scarier than this...