Closed Bug 1253508 Opened 8 years ago Closed 8 years ago

Let e10s jobs on trunk ride the trains

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(e10s+)

RESOLVED FIXED
Tracking Status
e10s + ---

People

(Reporter: jgriffin, Assigned: jgriffin)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Some e10s jobs are currently pinned to trunk; we should let them ride the trains now instead.
Attachment #8726576 - Flags: review?(catlee)
Assignee: nobody → jgriffin
Status: NEW → ASSIGNED
Pretty sure that'll give you multiple permaoranges on aurora47 - I've been starring them as expected fails on try pushes, presuming that we weren't letting those suites ride the trains because nobody had yet fixed the !NIGHTLY failures.
(In reply to Phil Ringnalda (:philor) from comment #2)
> Pretty sure that'll give you multiple permaoranges on aurora47 - I've been
> starring them as expected fails on try pushes, presuming that we weren't
> letting those suites ride the trains because nobody had yet fixed the
> !NIGHTLY failures.

Do you have any examples? If this happens, we can just hide the permaorange jobs temporarily while we fix or disable.
Looks like my memory is both stale, and confused between actual aurora-46 and 47 pushed as if it were aurora-47, which seems to now be greened up.
Attachment #8726576 - Flags: review?(catlee) → review+
Blocks: e10s-tests
tracking-e10s: --- → +
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: