If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

leaktest timeout should be shorter than buildbot timeout

RESOLVED FIXED in mozilla18

Status

Testing
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: karlt, Assigned: karlt)

Tracking

Trunk
mozilla18
x86_64
Linux
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
The current buildbot timeout for leaktest is 3600 apparently because this used to take a long time on winnt.
http://mxr.mozilla.org/build/source/buildbotcustom/process/factory.py#1313 

Bug 540369 also refers to this taking a long time, but trace-malloc now takes only 46 secs on WINNT 5.2 mozilla-central leak test build.

Not having a timeout here is preventing us getting a stack for bug 793016.
(Assignee)

Comment 1

5 years ago
Created attachment 663272 [details] [diff] [review]
set leaktest timeout to half buildbot timeout
Attachment #663272 - Flags: review?(ted.mielczarek)
(Assignee)

Updated

5 years ago
Blocks: 793016
Version: unspecified → Trunk
Comment on attachment 663272 [details] [diff] [review]
set leaktest timeout to half buildbot timeout

Review of attachment 663272 [details] [diff] [review]:
-----------------------------------------------------------------

r=me as long as this doesn't cause intermittent failures on tinderbox.
Attachment #663272 - Flags: review?(ted.mielczarek) → review+
(Assignee)

Comment 3

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/2f9d00b31660
Flags: in-testsuite-
(Assignee)

Comment 4

5 years ago
Unfortunately that landed 26 minutes too late to get any data for bug 794174.
Attachment 664586 [details] [diff] had already landed.
Yeah, once we got a stack there finding a workaround was easy enough.
https://hg.mozilla.org/mozilla-central/rev/2f9d00b31660
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
You need to log in before you can comment on or make changes to this bug.