As far as I understood the problem. Whenever the build was hanging, I could see a Flashplayer instance complaining about a timeout of 15 seconds having expired and if the user whiches to continue or cancel, hereby blocking the instance and the associated test.
I know that in flexmojos we wrapped a timout around the execution so we could kill the flashplayer if it didnt return in time. But as far as I saw the grid tests in mustella, the time each test takes is extremely extensive. A simple kill if the player is still active after 5 or 10 minutes won't do ... would have to be something more sophisticated as "if no test has responded for more than 30 seconds kill" and have the SWF report progress back to mustella. Chris -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Dienstag, 22. Juli 2014 22:30 An: dev@flex.apache.org; Erik de Bruin Betreff: Re: [VMs] Monitoring volunteer(s) needed I saw mention of a building timeout plug in for Jenkins. Would that help? Sent via the PANTECH Discover, an AT&T 4G LTE smartphone. Erik de Bruin <e...@ixsoftware.nl> wrote: Hi, I just checked both VMs, the one that provides the nightly builds for Flex and the other which runs the Mustella tests... Both haven't run a successful job in 14 days! I have updated and rebooted both machines, so for now all should be well, but especially the Mustella machine will bork after the first successful build, an issue that to my knowledge hasn't been fixed. Is there anyone out there that has some cycles to spare to monitor both VMs and their performance on perhaps a (semi)daily basis? EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
