|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

I again had something similar, now with 1.480.1. This time it looks even worse.
Background: We're doing a build on a slave, which creates big (4 times 700MB) artifacts, and the master archives them to a Windows share. (Note that I introduced both aspects at the same times: until recently these builds were done on the master, and archived on the master's C:-drive. Yes, I'm using Windows.)
In this new set-up one of the first builds had its console output end in
and then everything seems to break off: there is no Finished: line at the end. I could find not a single related log message, neither on the master or on the slave.
By comparison, a successful build+archive ends thusly:
I plan to upgrade to 1.509.2 soon. Is there any indication that archiving large files is more reliable currently? Or at least that archiving errors are / can be treated as build failures?
(And: If anyone is actually reading this, could they respond, so that I don't feel like I'm reporting issues into thin air? Thanks!)