Closed Bug 1264095 Opened 10 years ago Closed 10 years ago

test_page_errors.html is going to permafail when Gecko 48 merges to Aurora

Categories

(DevTools :: Console, defect)

defect
Not set
critical

Tracking

(firefox46 unaffected, firefox47+ fixed, firefox48+ fixed)

RESOLVED FIXED
Firefox 48
Tracking Status
firefox46 --- unaffected
firefox47 + fixed
firefox48 + fixed

People

(Reporter: ryanvm, Unassigned)

References

Details

Attachments

(1 file)

[Tracking Requested - why for this release]: Test permafail when Gecko 48 merges to Aurora. https://treeherder.mozilla.org/logviewer.html#?job_id=19229413&repo=try TEST-UNEXPECTED-FAIL | devtools/shared/webconsole/test/test_page_errors.html | errorMessage: /repeat count.*less than infinity/ matched SyntaxError: expected expression, got '*' TEST-UNEXPECTED-FAIL | devtools/shared/webconsole/test/test_page_errors.html | property 'errorMessageName' - got "JSMSG_UNEXPECTED_TOKEN", expected "JSMSG_RESULTING_STRING_TOO_LARGE"
Flags: needinfo?(winter2718)
(In reply to Ryan VanderMeulen [:RyanVM] from comment #0) > [Tracking Requested - why for this release]: Test permafail when Gecko 48 > merges to Aurora. > > https://treeherder.mozilla.org/logviewer.html#?job_id=19229413&repo=try > > TEST-UNEXPECTED-FAIL | devtools/shared/webconsole/test/test_page_errors.html > | errorMessage: /repeat count.*less than infinity/ matched SyntaxError: > expected expression, got '*' > TEST-UNEXPECTED-FAIL | devtools/shared/webconsole/test/test_page_errors.html > | property 'errorMessageName' - got "JSMSG_UNEXPECTED_TOKEN", expected > "JSMSG_RESULTING_STRING_TOO_LARGE" Something has caused the error I'd intended to trigger to change. This isn't a critical bug IMO, the test just needs to be updated. Investigating.
Flags: needinfo?(winter2718)
Sorry, this is "critical."
Verified working on Aurora locally.
Attachment #8740870 - Flags: review?(ryanvm)
So, this begs the question, why does say |2**2| now raise a syntax error. I'll ask tomorrow in JSAPI.
So, this begs the question, why does say |2**2| now raise a syntax error? I'll ask tomorrow in JSAPI.
(In reply to Morgan Phillips [:mrrrgn] from comment #5) > So, this begs the question, why does say |2**2| now raise a syntax error? > I'll ask tomorrow in JSAPI. I've seen failures like this before caused where language features are enabled only in Nightly builds
Terrence had a similar issue with ** in bug 1261649.
Comment on attachment 8740870 [details] [diff] [review] starstart-to-e.diff Review of attachment 8740870 [details] [diff] [review]: ----------------------------------------------------------------- Not sure I'm a legit reviewer here, but LGTM anyway :P
Attachment #8740870 - Flags: review?(ryanvm) → review+
(In reply to Ryan VanderMeulen [:RyanVM] from comment #8) > Comment on attachment 8740870 [details] [diff] [review] > starstart-to-e.diff > > Review of attachment 8740870 [details] [diff] [review]: > ----------------------------------------------------------------- > > Not sure I'm a legit reviewer here, but LGTM anyway :P What's the next step on this ? Request uplift or just merge to inbound ?
Just needs to land on inbound. 48 doesn't go to Aurora until the 25th.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 48
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: