Closed
Bug 1757240
Opened 3 years ago
Closed 3 years ago
Stop CI Builds of JS Streams
Categories
(Core :: DOM: Streams, task, P3)
Core
DOM: Streams
Tracking
()
RESOLVED
FIXED
100 Branch
Tracking | Status | |
---|---|---|
firefox100 | --- | fixed |
People
(Reporter: mgaudet, Assigned: mgaudet)
References
Details
Attachments
(1 file)
In preparation for removing MOZ_DOM_STREAMS code we should stop the CI builds that maintain the JS Streams code in Gecko.
Assignee | ||
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P3
Assignee | ||
Comment 1•3 years ago
|
||
We originally preserved a JS Streams build through a nightly cycle to
provide us with an emergency fallback position. However, it's increasingly
likely we will never take that fallback, and so we are faced with an increasing
dual maintenence burden.
Stopping CI builds is the first step of removing the JS streams code from Gecko,
and will prevent further noise on CI as the fallback position slowly loses relevance.
This patch is a backout of the build portion of Bug 1734722.
Updated•3 years ago
|
Assignee: nobody → mgaudet
Status: NEW → ASSIGNED
Pushed by mgaudet@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1820f90df625
Stop building JS Streams in CI r=firefox-build-system-reviewers,nalexander
Comment 3•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•