Closed
Bug 607852
Opened 15 years ago
Closed 14 years ago
Ensure talos/unittests run at least 2x per day
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: catlee, Unassigned)
References
Details
As per dev.tree-management discussion ("Using the same revision for nightly builds", beltzner's last post on July 17), once we stop doing nightly builds when then are no changes (esp. on stable branches; cf. bug 570814), we need to make sure that we get regular talos and test coverage.
Comment 1•14 years ago
|
||
Do we still want this?
Component: Release Engineering → Release Engineering: Automation
QA Contact: release → catlee
Comment 2•14 years ago
|
||
Absolutely not. Rereading the thread, it didn't actually make any sense at the time (talos doesn't vary over time, and if we need more runs per code change to eliminate noise then we need them on every push, not just on pushes which sit without getting another push after them), but in a world with self-serve in it, it makes absolutely no sense at all. In the one case out of never when someone needs twenty extra talos runs on a 1.9.2 push that didn't have another push after it for ten days, they can trigger those twenty extra runs.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
| Assignee | ||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•