Closed Bug 854407 Opened 12 years ago Closed 12 years ago

Give the "child process NNNN still alive after shutdown" failure a unique test name

Categories

(Testing :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla22

People

(Reporter: emorley, Assigned: emorley)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Bug 603147 is a manual star, frequent and annoying. We should make the failure line: TEST-UNEXPECTED-FAIL | automation.py | child process %d still alive after shutdown something like: TEST-UNEXPECTED-FAIL | zombiecheck | child process %d still alive after shutdown So that we don't blacklist bug suggestions due to using the (not unique enough) 'automation.py' test name.
Attachment #728981 - Flags: review?(jmaher)
Comment on attachment 728981 [details] [diff] [review] s/automation.py/zombiecheck/ Review of attachment 728981 [details] [diff] [review]: ----------------------------------------------------------------- ::: build/automation.py.in @@ +1137,5 @@ > # Whilst no hung process was found, the run should still display as a failure > return True > > foundZombie = False > + self.log.info('INFO | zombiecheck | Reading PID log: %s', processLog) I really don't like this name, but it is descriptive and I do not have a suitable recommendation for an alternative.
Attachment #728981 - Flags: review?(jmaher) → review+
Yeah I couldn't think of anything more appropriate either. Thanks for the review :-) https://hg.mozilla.org/integration/mozilla-inbound/rev/c039f412b785
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: