Closed
Bug 488732
Opened 16 years ago
Closed 16 years ago
Do multiple unittest runs on a single build
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: catlee)
References
Details
Attachments
(3 files, 1 obsolete file)
3.52 KB,
patch
|
bhearsum
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
2.59 KB,
patch
|
bhearsum
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
6.33 KB,
patch
|
nthomas
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
It would be useful to get multiple test runs of a single build on occasion to be able to track down tests that fail intermittently. By testing the same build, we can be sure that a change in the code isn't causing a different in test results.
Assignee | ||
Comment 1•16 years ago
|
||
This scheduler will trigger rebuilds of previous builds on the specified builders, at the given times. By default it will trigger one rebuild, but be told to rebuild more than once.
Attachment #381140 -
Flags: review?(bhearsum)
Updated•16 years ago
|
Attachment #381140 -
Flags: review?(bhearsum) → review+
Comment 2•16 years ago
|
||
Comment on attachment 381140 [details] [diff] [review]
NightlyRebuild scheduler
Seems fine to me. Do you think this is something that is upstreamable or is it Mozilla-specific?
Assignee | ||
Comment 3•16 years ago
|
||
Attachment #382111 -
Flags: review?(bhearsum)
Comment 4•16 years ago
|
||
Comment on attachment 382111 [details] [diff] [review]
Re-test packaged builds on staging once per night
Looks fine to me
Attachment #382111 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 5•16 years ago
|
||
Attachment #382111 -
Attachment is obsolete: true
Attachment #384204 -
Flags: review?(bhearsum)
Updated•16 years ago
|
Attachment #384204 -
Flags: review?(bhearsum) → review+
Comment 6•16 years ago
|
||
Comment on attachment 384204 [details] [diff] [review]
Re-test packaged builds every week.
Nits:
>diff --git a/mozilla2-staging/master-main.cfg b/mozilla2-staging/master-main.cfg
>+ numberOfBuildsToTrigger=1, mergeBuilds=False))
You may use 2 lines.
>diff --git a/mozilla2/master.cfg b/mozilla2/master.cfg
>+ numberOfBuildsToTrigger=2,
(Do you really want '2'?)
Assignee | ||
Comment 7•16 years ago
|
||
Comment on attachment 381140 [details] [diff] [review]
NightlyRebuild scheduler
changeset: 346:0bc6e7a9f350
Attachment #381140 -
Flags: checked‑in+
Assignee | ||
Comment 8•16 years ago
|
||
Comment on attachment 384204 [details] [diff] [review]
Re-test packaged builds every week.
changeset: 1225:0c07f03ec90f
Attachment #384204 -
Flags: checked‑in+
Assignee | ||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 9•15 years ago
|
||
going to disable this since it's been causing semi-random redness, and nobody is looking at the results anyway.
Attachment #424282 -
Flags: review?(nrthomas)
Updated•15 years ago
|
Attachment #424282 -
Flags: review?(nrthomas) → review+
Assignee | ||
Comment 10•15 years ago
|
||
Comment on attachment 424282 [details] [diff] [review]
disable nightly rebuilds
changeset: 599:fb5543bb7a4a
Attachment #424282 -
Flags: checked-in+
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•