Closed Bug 562080 Opened 10 years ago Closed 10 years ago

mochitest-plain-2: test_bug509055.html reports 2 "JavaScript error: [...] hashchangeCallback is not defined"

Categories

(Core Graveyard :: History: Global, defect, minor)

x86
macOS
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.9.3a5

People

(Reporter: sgautherie, Assigned: justin.lebar+bug)

References

()

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1272382319.1272384041.2123.gz&fulltext=1
Rev3 MacOSX Leopard 10.5.8 mozilla-central debug test mochitests-2/5 on 2010/04/27 08:31:59
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1272384266.1272386065.10359.gz&fulltext=1
OS X 10.5 comm-central-trunk debug test mochitests-2/5 on 2010/04/27 09:04:26
{
JavaScript error: http://mochi.test:8888/tests/docshell/test/file_bug509055.html, line 1: hashchangeCallback is not defined
JavaScript error: http://mochi.test:8888/tests/docshell/test/file_bug509055.html, line 1: hashchangeCallback is not defined
}
and has other warnings too...
Summary: test_bug509055.html reports 2 "JavaScript error: [...] hashchangeCallback is not defined" → mochitest-plain-2: test_bug509055.html reports 2 "JavaScript error: [...] hashchangeCallback is not defined"
I can reproduce locally.  I think this is just a bug in the test and not indicative of actual breakage.
Blocks: 515190
No longer blocks: 509055
Attached patch Fix (obsolete) — Splinter Review
This was an oversight when I fixed bug 515190.
Assignee: nobody → justin.lebar+bug
Status: NEW → ASSIGNED
Attachment #442015 - Flags: review?(Olli.Pettay)
Attachment #442015 - Flags: review?(Olli.Pettay) → review+
Keywords: regression
Attachment #442015 - Attachment is obsolete: true
Keywords: checkin-needed
http://hg.mozilla.org/mozilla-central/rev/2e29314a2776
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a5
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.