Remove cb-sea-linux-tbox, cb-seamonkey-linux-* from buildbot configuration

RESOLVED FIXED

Status

SeaMonkey
Release Engineering
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: ewong, Assigned: ewong)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

6 years ago
Since cb-sea-linux-tbox is sea-vm-linux32-1,  and bug 768379 added sea-vm-linux32-(1,2) to the configuration, and was subsequently switched on to
production,  cb-sea-linux-tbox can be removed from the configuration.
(Assignee)

Comment 1

6 years ago
Created attachment 640480 [details] [diff] [review]
Remove cb-sea-linux-tbox from buildbot configuration.
Attachment #640480 - Flags: review?(bugspam.Callek)
(Assignee)

Updated

6 years ago
OS: Windows 7 → Linux
Summary: Remove cb-sea-linux-tbox from buildbot configuration → Remove cb-sea-linux-tbox, cb-seamonkey-linux-* from buildbot configuration
(Assignee)

Comment 2

6 years ago
Created attachment 640505 [details] [diff] [review]
Remove cb-sea-linux-tbox, cb-seamonkey-linux-* from buildbot configuration.
Attachment #640480 - Attachment is obsolete: true
Attachment #640480 - Flags: review?(bugspam.Callek)
Attachment #640505 - Flags: review?(bugspam.Callek)
Comment on attachment 640505 [details] [diff] [review]
Remove cb-sea-linux-tbox, cb-seamonkey-linux-* from buildbot configuration.

Review of attachment 640505 [details] [diff] [review]:
-----------------------------------------------------------------

While we are here, can you increase the range for sea-vm-linux32-X  I suggest we use |range(1,7)| instead of manually doing [1,2,...] for this.

You can take my r+ to include that change, or write a new patch for that change, your call.

When you land, please do *two* reconfigs in a row.
Attachment #640505 - Flags: review?(bugspam.Callek) → review+
(Assignee)

Updated

6 years ago
Blocks: 773553
(Assignee)

Comment 4

6 years ago
Pushed to buildbot-configs:
http://hg.mozilla.org/build/buildbot-configs/rev/4379b0110d1b
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.