torsdag 8. mars 2018 12.37.47 UTC+1 skrev Reinhold Füreder følgende: > > Very naïve thought(s): > > > > While “*Do not know why nodeName1 acquired the lock before nodeName > released.*“ might be just a matter of output flushing/buffering, > I thought so also, probably because of parallell execution.
“*The entire build hangs and goes no further.*” sounds really frightening > to me. > > > > Maybe it is the usage of lock inside parallel step and/or some CPS > transformation reason, or some little resource misconfiguration issue!? > > > > Ignoring CPS transformations (due to parallel step) I assume/hope the lock > plugin does unit testing the “normal” parallelization usage of locking > resources? > Perhaps a bug in Lockable Resource Plugin. There is no output of CPS transformation exception, nor any other error output. It just hangs after the first acquired resource lock is finished. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b7baa7e7-4042-4792-873b-6a1f47f8cf83%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
