Closed
Bug 1319512
Opened 9 years ago
Closed 8 years ago
Disable non-standard expression closure on nightly-only
Categories
(Core :: JavaScript Engine, defect, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla59
Tracking | Status | |
---|---|---|
firefox59 | --- | fixed |
People
(Reporter: arai, Assigned: evilpies)
References
Details
(Keywords: dev-doc-complete, site-compat, triage-deferred)
Attachments
(2 files)
949 bytes,
patch
|
jandem
:
review+
|
Details | Diff | Splinter Review |
12.24 KB,
patch
|
jandem
:
review+
|
Details | Diff | Splinter Review |
Just like bug 1293305, we could disable it only on nightly, with runtime flag,
and keep tests working with testing function to enable it (enableExprClosure).
some tests that want to test expression closure should call enableExprClosure,
and other tests that don't need expression closure should be rewritten in bug 1313490.
Updated•9 years ago
|
Keywords: dev-doc-needed
Updated•8 years ago
|
Keywords: site-compat
Updated•8 years ago
|
Keywords: triage-deferred
Priority: -- → P3
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → evilpies
Assignee | ||
Comment 1•8 years ago
|
||
Attachment #8928478 -
Flags: review?(jdemooij)
Assignee | ||
Comment 2•8 years ago
|
||
A while ago we had a few failures on Try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=cd5621a92f4134d19781cf0881b097d8dde80de1&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-classifiedState=unclassified&selectedJob=144000446
I am going to rerun this later, to see if this is real.
Attachment #8928479 -
Flags: review?(jdemooij)
Updated•8 years ago
|
Attachment #8928478 -
Flags: review?(jdemooij) → review+
Comment 3•8 years ago
|
||
Comment on attachment 8928479 [details] [diff] [review]
Adjust expression closure tests so they fail
Review of attachment 8928479 [details] [diff] [review]:
-----------------------------------------------------------------
Great we can turn this off finally. We just need to remember to remove these tests when we remove expression closures.
::: js/src/tests/js1_8_5/reflect-parse/expressionClosures.js
@@ +1,1 @@
> +// |reftest| skip-if(!xulRuntime.shell) skip-if(!release_or_beta)
Does this work or should it be:
// |reftest| skip-if(!xulRuntime.shell || !release_or_beta)
Attachment #8928479 -
Flags: review?(jdemooij) → review+
Pushed by evilpies@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/261ebf2e8bbd
Disable expression closures on Nightly. r=jandem
https://hg.mozilla.org/integration/mozilla-inbound/rev/8d8aeee2633f
Adjust expression closure tests. r=jandem
Comment 6•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/261ebf2e8bbd
https://hg.mozilla.org/mozilla-central/rev/8d8aeee2633f
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox59:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Comment 7•8 years ago
|
||
Updated the site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2015/expression-closure-support-will-be-removed/
Comment 8•8 years ago
|
||
Tom, what do you want to do here on beta/release? Our options are:
(1) Disable expression closures unconditionally on Nightly so this will ride the trains.
(2) Uplift a patch after the merge.
(3) Disable expression closures on beta 58 (too late for that now I guess).
(4) Remove expression closures on Nightly.
I don't care too much, but we should do one of these so this will stay disabled on beta.
Flags: needinfo?(evilpies)
Comment 10•8 years ago
|
||
Keywords: dev-doc-needed → dev-doc-complete
Updated•7 years ago
|
status-firefox53:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•