I have several jobs that finish for all intents and purposes, but Jenkins doesn't recognize it.
Server and client are running on different Linux machines, using Java 7 (and the server is using the embedded winstone server). The job is done; the log says "build finished", the slave node has no subordinate jobs, and the only files the slave has are stdin/out/err connections to the script that launches it, /dev/random and /dev/urandom, and various JAR files. I shut down the client (verifying that the slave job no longer exists) and the job is still listed as running. I re-launched the slave, and it still thinks it's running that job. And it will think that it's still running the job until it hits the job timeout, where it will declare the build successful (not aborted). Having the job survive a client bounce suggests that this is a failure in Jenkins accounting on the server side. Has anybody else run into this, and is there a workaround? Thanks in advance, --Rob The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
