I just posted a reply to this thread and somehow the message got deleted. I see
<https://lh3.googleusercontent.com/-mh1tfDgW9wk/WrLUmbuPz7I/AAAAAAAAAuY/aGlNOyeG8JghFJfBxIsG31vUf3NlECV8gCLcBGAs/s1600/Screen%2BShot%2B2018-03-21%2Bat%2B23.53.10.png> <https://lh3.googleusercontent.com/-mh1tfDgW9wk/WrLUmbuPz7I/AAAAAAAAAuY/aGlNOyeG8JghFJfBxIsG31vUf3NlECV8gCLcBGAs/s1600/Screen%2BShot%2B2018-03-21%2Bat%2B23.53.10.png> Have I did something wrong? On Wednesday, March 21, 2018 at 5:32:21 PM UTC+2, Jesse Glick wrote: > > On Wed, Mar 21, 2018 at 7:12 AM, Daniel Anechitoaie > <[email protected] <javascript:>> wrote: > > [Is it] possible maybe one of these libraries? […] > > > > I tried a test with just a bunch of Thread.sleep() before it gets to my > code > > (that zips the files and HTTP puts them) and if I cancel the job there > it > > gets aborted nicely and is handled properly by Jenkins. > > So sounds like a problem in the interaction between the behavior of > those libraries and Jenkins interrupt handling. Again I suspect that > something is catching interrupts, proceeding without throwing > `InterruptedException`, but then setting the thread interrupt flag and > this gets ignored up until the moment the build record is being > finalized and the NIO calls made from `AtomicFileWriter` check the > flag. If true, the solution would probably be for the code which runs > an individual build step (somewhere in `AbstractBuild` IIRC) to check > the interrupt flag and throw `InterruptedException` at that time. > Could be verified in a `JenkinsRule`-based test by having a > `TestBuilder` which mimics the relevant behavior of these libraries. > > I doubt this particular issue could apply to Pipeline builds, though > there might be other ways in which interrupt handling is incorrect > there as well. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/3e269568-7fa9-4743-b845-e7764eaac4bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
