Closed
Bug 539135
Opened 15 years ago
Closed 15 years ago
Tracking bug for scheduled downtime (14-jan-2010)
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: anodelman)
References
(Depends on 1 open bug)
Details
As experiment, lets track as dep.bugs all the work that need doing in next downtime.
Intentionally, leaving in triage queue for now. Whomever is point person for this downtime should claim this bug.
Assignee | ||
Updated•15 years ago
|
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → anodelman
Summary: Tracking bug for scheduled downtime (14-jan-2010?) → Tracking bug for scheduled downtime (14-jan-2010)
Assignee | ||
Comment 1•15 years ago
|
||
Notification posted in appropriate newsgroups.
Assignee | ||
Comment 2•15 years ago
|
||
Scheduled for 8-11am PST, Thursday January 14th.
Assignee | ||
Comment 3•15 years ago
|
||
All patches checked in.
Tp4 bustage required extra patches in winmo bugs to get cmanager_mac/linux working again.
Assignee | ||
Comment 4•15 years ago
|
||
Tp4 boxes on linux running the test to completion, but talos not closing at the end of test run. Leaves talos linux slaves in a hung state.
Investigating for possible bustage fix.
Assignee | ||
Comment 5•15 years ago
|
||
bustage fix, disabling Xres collection:
Checking in sample.config;
/cvsroot/mozilla/testing/performance/talos/sample.config,v <-- sample.config
new revision: 1.40; previous revision: 1.39
done
Assignee | ||
Comment 6•15 years ago
|
||
Bustage fix successful.
Bug 539806 to get xres collection turned back on.
Assignee | ||
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
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
•