On Fri, Feb 1, 2019 at 2:31 AM Steven Foster <stevengfos...@gmail.com> wrote:
> After updating Jenkins with plugins from early April 2018, I'm seeing > inconsistent failures in my pipelines' calls to MSBuild which I cannot > reproduce outside of Jenkins. It occurs in both powershell and bat steps. > > The error presents as > > 0>MSBUILD : error MSB4166: Child node "14" exited prematurely. Shutting > down. Diagnostic information may be found in files in the temporary files > directory named MSBuild_*.failure.txt. > > There is no such extra information file. This looks a bit like an > interrupt to me, is there a way I can reproduce how Jenkins sends > interrupts so I can verify that? > Are there any advanced durable task debugging techniques I could use to > find out what could be causing an interrupt or something else? > We had a similar issue, and it ended up being related to MSBuild itself, not Jenkins. The jobs seemed to work correctly when run from a command line, but it took a while and they eventually started failing as well. Our issue was due to the maximum number of temp files in %TEMP% being exceeded (see the GetTempFileNameA[1] function, it has an internal limit of 65,535). Once we cleared those out (and resolved the bug in our code that wasn't cleaning them up), the builds worked again. [1] - https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi-gettempfilenamea -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAJM0iSQNCSNi3Z0oQSfZTJD9ZmbjKwCyNO8VNuhgimiXDwLk8Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
