468026 - tinderboxes don't pick up changes to tinderbox script automatically

Status: RESOLVED WONTFIX

(NSS :: Test, defect, P2)

Description

[Nelson Bolyard (seldom reads bugmail)]

When changes to the NSS tinderbox scripts are checked in, they have
no effect until someone manually intervenes on every tinderbox build
system to make the tinderboxes start using the new script. 
They seem to just keep using the same old script over and over. 

What should happen, starting ASAP, is that they should replace the 
tinderbox script being run with the newly checked out one, so that 
on the next cycle, they will run the new script automatically, 
without human intervention.

Comment 1

[Slavomir Katuscak]

Tinderbox tests are specific that they sometimes need to be tested carefully only on one or few machines to catch bugs in them and after I'm sure that they are OK I apply changes (cvs udpate) on all machines. Therefore I would rather not use automatic update. 

I implemented a different solution, I have the script tbcheck.sh with list of all supported tinderbox machines that runs every hour from cron on machine mace and restarts hanged tinderboxes (or start them if they are not running). This script can be easily modified to kill all running tests, update tinderboxes and restart them back (this code is already there, but is commented out). When I want to update all machines, I use this solution, and it is controlled, so I don't mess all Tinderboxes when something is wrong and it haven't been tested enough yet.