Skip to main content

[Hudson-Dev] Re: Update on the hudson-test-harness work...

  • From: Winston Prakash <winston.prakash@...>
  • To: dev@...
  • Cc: Jason Dillon <jason@...>
  • Subject: [Hudson-Dev] Re: Update on the hudson-test-harness work...
  • Date: Thu, 24 Feb 2011 14:36:30 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=N+PGuM7a5v4VyKHF7oM4Asbji6qjqn3g8zQfS7IS/jJ35fWgaNU1L56SsP4usHxZbu LQXPp7/hI3YR8d6cfHk9xoH5Knx6aBNDxFyKkJIjQg4nxScBuFtVJI52SuR0HZ+9hRoA Q73iUN3kCwmOPVVZo+Cmxch/uaWAFST+4E43Y=

On my Mac it took about 45 mins. You are right hudson.slaves.JNLPLauncherTest was hanging (only on MAC) and I always kill that manually.

- Winston
Its still not fully passing (in, but I was 
finally able to get it to at least always complete (and not kill the mvn 
process mid-build) on my mac:

Tests run: 840, Failures: 26, Errors: 3, Skipped: 0

[INFO] Total time: 45:14.077s
[INFO] Finished at: Thu Feb 24 13:58:41 PST 2011
[INFO] Final Memory: 32M/124M

Many of these are failures in the m2/3 job type, or failures due to tests 
using those features.

One test, hudson.slaves.JNLPLauncherTest, was forced to timeout after 5 
minutes.  I had to set forkMode always and configure the fork timeout.

Anyone know how long the hudson-test-harness took before when it was on a 
system that didn't hang when doing slave/remoting stuff?


[Hudson-Dev] Update on the hudson-test-harness work...

Jason Dillon 02/24/2011

[Hudson-Dev] Re: Update on the hudson-test-harness work...

Winston Prakash 02/24/2011
Please Confirm