Opened 4 years ago

#3486 new undecided

Interrupted a builder that was waiting for a lock (running another build with the lock), lock was never released

Reported by: RockHed Owned by:
Priority: major Milestone: undecided
Version: 0.8.12 Keywords: locks


My slave allows a max of 2 builds, but I use SlaveLock? on certain steps. At one point, a build was running that took the lock, and another build was waiting for the lock. I had to interrupt the build that was waiting, and I also had to restart the slave around the same time. As a result, after it came up, all builds were stuck in waiting for that lock, so it seems somewhere it was taken and not released.

Work-around is to rename the lock and reconfigure, and possibly stop/start the master (untested yet) with the original config.

Change History (0)

Note: See TracTickets for help on using tickets.