Closed Bug 902014 Opened 12 years ago Closed 12 years ago

jsbeautifier is broken

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 897904
Tracking Flags:
Tracking Status
firefox25 - ---

People

(Reporter: bzbarsky, Unassigned)

References

Details

(Keywords: regression)

I don't know what broke it yet, but it shows nothing at all. This regressed in this range on m-c nightlies: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3d40d270c031&tochange=c2b375f3a909 I tried bisecting on hourlies and hg claimed that a merge changeset is responsible. :( Bisecting on actual builds now.
Hmm. This seems to be reproducible only sort of reliably... sometimes. Maybe better regression range: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c0830a5933e8&tochange=04d8c309fe72 which now matches the regression range in bug 897904?
Depends on: 897904
qawanted to see if others are able to reproduce on http://jsbeautifier.org/, and to see if we can finish the regressionwindow-wanted that bz was doing before his vacation.
Keywords: qawanted, regressionwindow-wanted
I suspect this bug is a duplicate of bug 897904, which has an exact regressing changeset.
And a patch, for that matter.
Yep, just came back upon that.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Dropping *wanted keywords since it appears those requests are moot given comment 3.
Keywords: qawanted, regressionwindow-wanted
You need to log in before you can comment on or make changes to this bug.