651979 - jetpack tests took 272s but keeps running until buildbot times out after ~1600s

Status: RESOLVED FIXED

(Add-on SDK Graveyard :: General, defect, P1)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

This is taking up a lot of extra machine time on an already overloaded pool, and its running on many branches and platforms.

bash -c '/Users/cltbld/talos-slave/test/tools/buildfarm/utils/run_jetpack.sh macosx64'


and ends up with

nsStringStats
 => mAllocCount:         801236
 => mReallocCount:        15354
 => mFreeCount:          801236
 => mShareCount:         787846
 => mAdoptCount:          81633
 => mAdoptFreeCount:      81633
Total time: 272.490047 seconds
Program terminated successfully.
All tests were successful. Ship it!

command timed out: 1200 seconds without output, attempting to kill
program finished with exit code -1
elapsedTime=1538.567008



http://buildbot-master2.build.scl1.mozilla.com:8011/builders/Rev3%20MacOSX%20Snow%20Leopard%2010.6.2%20mozilla-central%20debug%20test%20jetpack/builds/12/steps/jetpack/logs/stdio

(you might not be able to see that log, but including it here so we don't loose it)

Comment 1

[Myk Melez [:myk] [@mykmelez]]

I can see the log.  Strange.  It looks different from bug 651665, although I suppose it could be a different manifestation of the same problem.

It's definitely intermittent, since other runs finish up once tests succeed:

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1303410352.1303410732.29965.gz&fulltext=1

John: do you know how often this happens?

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

(In reply to comment #1)
> I can see the log.  Strange.  It looks different from bug 651665, although I
> suppose it could be a different manifestation of the same problem.
> 
> It's definitely intermittent, since other runs finish up once tests succeed:
> 
> http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1303410352.1303410732.29965.gz&fulltext=1
> 
> John: do you know how often this happens?

I only noticed it because it blocked a reconfig for 20 minutes.

Comment 3

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

from irc with lsblakk, pushing this to myk, as we believe a) this is a genuine product problem and b) myk has a workaround ready.

Comment 4

[Myk Melez [:myk] [@mykmelez]]

I haven't seen this since it was initially reported.  Has anyone else?

Comment 5

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Hearing no objections... I'm gonna close this.

Reopen or re-file if you disagree. :)