Closed Bug 432858 Opened 16 years ago Closed 16 years ago

add qm-xserve06 to staging then production

Categories

(Release Engineering :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rcampbell, Assigned: rcampbell)

References

Details

Attachments

(2 files, 3 obsolete files)

[checked in] xserve06 staging patch 3
26.07 KB, patch
Details | Diff | Splinter Review
[checked in] xserve06 production patch
4.46 KB, patch
nthomas
: review+
Details | Diff | Splinter Review 
trial runs on staging for qm-xserve06
Attached patch qm-xserve06 staging (obsolete) — — Splinter Review 
patch to add it to staging
Assignee: nobody → rcampbell
Status: NEW → ASSIGNED
Attachment #320022 - Flags: review?(bhearsum)
Attachment #320022 - Flags: review?(bhearsum) → review+
Attached patch xserve06 staging patch 2 (obsolete) — — Splinter Review 
staging environment wildly out of sync with cvs, created new patch to reflect reality.
Attachment #320022 - Attachment is obsolete: true
Attachment #320025 - Flags: review?(bhearsum)
Attached patch xserve06 staging patch 2 (obsolete) — — Splinter Review 
some crud at the end of the patch file removed
Attachment #320025 - Attachment is obsolete: true
Attachment #320025 - Flags: review?(bhearsum)
wrong slavename. corrected.
Attachment #320026 - Attachment is obsolete: true
running on staging, creating a patch to shift machine to production.
Summary: add qm-xserve06 to staging → add qm-xserve06 to staging then production
Comment on attachment 320050 [details] [diff] [review]
[checked in] xserve06 staging patch 3

cvs commit: Examining .
Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/testing/unittest-stage/master.cfg,v  <--  master.cfg
new revision: 1.7; previous revision: 1.6
done
Attachment #320050 - Attachment filename: xserve06-staging3.patch → [checked in] xserve06-staging3.patch
Attachment #320050 - Attachment description: xserve06 staging patch 3 → [checked in] xserve06 staging patch 3
production lines
Attachment #320065 - Flags: review?(bhearsum)
Attachment #320065 - Flags: review?(bhearsum) → review+
Comment on attachment 320065 [details] [diff] [review]
[checked in] xserve06 production patch

Checking in auth.py;
/cvsroot/mozilla/tools/buildbot-configs/testing/unittest/auth.py,v  <--  auth.py
new revision: 1.6; previous revision: 1.5
done
Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/testing/unittest/master.cfg,v  <--  master.cfg
new revision: 1.31; previous revision: 1.30
done
Attachment #320065 - Attachment description: xserve06 production patch → [checked in] xserve06 production patch
note: the first build after it was moved passed all tests. Every build after that has failed with the following that no other systems during this time have failed with:
REFTEST UNEXPECTED FAIL (LOADING): file:///builds/slave/trunk_osx_6/mozilla/layout/reftests/bugs/413292-1.html
Blocks: 432954
(In reply to comment #9)
> note: the first build after it was moved passed all tests. Every build after
> that has failed with the following that no other systems during this time have
> failed with:
> REFTEST UNEXPECTED FAIL (LOADING):
> file:///builds/slave/trunk_osx_6/mozilla/layout/reftests/bugs/413292-1.html
> 

I filed bug 432954 for this issue.
I'm marking this fixed for now. We can track the mysteriously failing reftest in bug 432954. Thanks for filing that, Dan.
Status: ASSIGNED → RESOLVED
Closed: 16 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.

Attachment

General

Creator:
Created:
Updated:
Size: