If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Need buildbot configs for new ref platform VM

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
10 years ago
4 years ago

People

(Reporter: rc, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
Created attachment 271829 [details] [diff] [review]
unittest.patch

Need an updated configuration to accomodate the new machine qm-centos5-01. Adding reftest prefs.js file as well.
Attachment #271829 - Flags: review?(preed)

Comment 1

10 years ago
Comment on attachment 271829 [details] [diff] [review]
unittest.patch

This looks fine; where is prefs.js gonna go? in buildbot-configs/testing/unittest?

(That's a fine place for it; I just didn't see a path in the patch).
Attachment #271829 - Flags: review?(preed) → review+
(Reporter)

Comment 2

10 years ago
yeah, I was just going to stick it into bbot-configs/testing/unittest to have a place for it. Eventually I'll add some buildbot-fu to generate those on first run but that's good enough for now. Thanks for the r. :)
(Reporter)

Comment 3

10 years ago
this was checked in, Aug 7, 2007
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.