You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Erik de Bruin <er...@ixsoftware.nl> on 2014/07/22 19:48:58 UTC
[VMs] Monitoring volunteer(s) needed
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
AW: [VMs] Monitoring volunteer(s) needed
Posted by Christofer Dutz <ch...@c-ware.de>.
How does the Mustella testrunner actually work?
In flexmojos we grab a socket and compile that socket number into the test-swf. The test swfs contain test-listeners depending on the unit-test framework used that connect to that socket and report back to the server how the tests went. Here whenever something is received we reset a timer. If that timer expires the process is killed. I think that would be quite good for the Mustella tests too as it doesn't measure the overall test duration, but how long a single test takes. That should work for the DataGrid tests (At least I watched about 100 different tests running there in one Flashplayer instance).
Chris
________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Mittwoch, 23. Juli 2014 08:11
An: dev@flex.apache.org
Betreff: Re: [VMs] Monitoring volunteer(s) needed
On 7/22/14 2:49 PM, "Michael A. Labriola" <la...@digitalprimates.net>
wrote:
>>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 never finished it but we were playing with a watch dog for FlexUnit so
>that the test runner sent a heartbeat message back to a monitoring
>instance (the java process that launched it) every (n) frames. Then we
>could configure the amount of time it was okay to go without the
>heartbeat. The difference being we would wait so long as Flash Player was
>still well enough to send its heartbeat. When it ceased, we would kill it.
In the mustella code is a .c source code for KillWin, something I wrote
for Windows that used to be able to kill off the player. I haven't tried
on recent players. But I haven't seen stuck player on the builds machine.
We're having different issues there.
-Alex
Re: [VMs] Monitoring volunteer(s) needed
Posted by Alex Harui <ah...@adobe.com>.
On 7/22/14 2:49 PM, "Michael A. Labriola" <la...@digitalprimates.net>
wrote:
>>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 never finished it but we were playing with a watch dog for FlexUnit so
>that the test runner sent a heartbeat message back to a monitoring
>instance (the java process that launched it) every (n) frames. Then we
>could configure the amount of time it was okay to go without the
>heartbeat. The difference being we would wait so long as Flash Player was
>still well enough to send its heartbeat. When it ceased, we would kill it.
In the mustella code is a .c source code for KillWin, something I wrote
for Windows that used to be able to kill off the player. I haven't tried
on recent players. But I haven't seen stuck player on the builds machine.
We're having different issues there.
-Alex
RE: [VMs] Monitoring volunteer(s) needed
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
>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 never finished it but we were playing with a watch dog for FlexUnit so that the test runner sent a heartbeat message back to a monitoring instance (the java process that launched it) every (n) frames. Then we could configure the amount of time it was okay to go without the heartbeat. The difference being we would wait so long as Flash Player was still well enough to send its heartbeat. When it ceased, we would kill it.
Mike
AW: [VMs] Monitoring volunteer(s) needed
Posted by Christofer Dutz <ch...@c-ware.de>.
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:aharui@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 <er...@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
Re: [VMs] Monitoring volunteer(s) needed
Posted by Alex Harui <ah...@adobe.com>.
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 <er...@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