Closed
Bug 471754
Opened 17 years ago
Closed 17 years ago
moz2-win32-slave13 got itself stuck on the 191b2_RELBRANCH
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: nthomas)
References
()
Details
moz2-win32-slave13 is burning "WINNT 5.2 mozilla-1.9.1 unit test %" after getting itself confused by an accidental checkin to the GECKO191b2_20081125_RELBRANCH, which has now left it hanging there, building revision 4f216e3d60cf over and over again since it lacks enough sense to |hg update -r default|.
I presume you don't have instructions for updating (or blowing away) repos, but perhaps it can be shut down to keep it from grabbing jobs and burning up the tree, before passing it on to build?
| Assignee | ||
Updated•17 years ago
|
Assignee: server-ops → nthomas
Component: Server Operations: Tinderbox Maintenance → Release Engineering: Maintenance
Priority: -- → P2
QA Contact: mrz → release
| Assignee | ||
Comment 1•17 years ago
|
||
cltbld@MOZ2-WIN32-SLAV /e/builds/moz2_slave/mozilla-1.9.1-win32-unittest/build
$ hg update -r default
1379 files updated, 0 files merged, 158 files removed, 0 files unresolved
$ hg branch
default
$ hg identify
cda265c626be tip
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•