|
||||||||
|
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.
Also, I think this problem only happens when a PR is being tested and there is a push -f in the same PR, so a new build is queued. After that happens, the build seems to stay broken.
Any idea about how this push -f while the PR is being tested can end up in this situation? Is any information about the hash being stored somewhere that is read then by the queued build for the same PR?