Closed Bug 539135 Opened 15 years ago Closed 14 years ago

Tracking bug for scheduled downtime (14-jan-2010)

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
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.
Depends on: 535027, 537526
Depends on: 535740
Depends on: 452861
Assignee: nobody → anodelman
Summary: Tracking bug for scheduled downtime (14-jan-2010?) → Tracking bug for scheduled downtime (14-jan-2010)
Notification posted in appropriate newsgroups.
Scheduled for 8-11am PST, Thursday January 14th.
All patches checked in.

Tp4 bustage required extra patches in winmo bugs to get cmanager_mac/linux working again.
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.
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
Bustage fix successful. 

Bug 539806 to get xres collection turned back on.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.