Tinderbox Orange on "OS X 10.5.2 mozilla-1.9.1 unit test": test_bug350471.xul fails. It seems to have started around 2009-02-20 23:00. *** 18783 ERROR TEST-UNEXPECTED-FAIL | /tests/content/events/test/test_bug350471.xul | normal DOMMouseScroll: only scroll if neither line nor pixel scroll are consumed. wrong scroll position - type: DOMMouseScroll - Expected 3950 to 3900, got 4000 etc.... Full Log: http://tinderbox.mozilla.org/showlog.cgi?tree=Firefox3.1&errorparser=unittest&logfile=1235238647.1235241919.10219.gz&buildtime=1235238647&buildname=OS%20X%2010.5.2%20mozilla-1.9.1%20unit%20test&fulltext=1
I've checked in a bunch of JS stuff, but I've never seen this test fail before.
I don't see any checkin that could cause this test to fail, so it's probably a problem with the test. I'll look into this.
Assignee: nobody → mstange
Status: NEW → ASSIGNED
This problem causes an orange roughly once every 2-3 cycles in the 1.9.1 tree. Under 10.5.6, couldn't duplicate this with my build. Not sure why this fails or how to reproduce the problem so I neutered this test until it can be investigated: http://hg.mozilla.org/releases/mozilla-1.9.1/rev/7c43ac8cccbd I can't quite figure out why JS changes would cause this...
Severity: normal → major
Priority: -- → P2
It's not an issue with bug 478536 that didn't manifest right away?
I don't think so; bug 442774 hasn't landed on 1.9.1 yet. I'll get to this tomorrow.
pushed follow-on patch to force remaining intermittent failures to succeed: http://hg.mozilla.org/releases/mozilla-1.9.1/rev/74caf8060538
This makes the test open a window, so we don't have to deal with the scroll transaction stuff that might make us scroll the testharness document instead of the scrollbox. The patch is against mozilla-central.
Attachment #364934 - Flags: review?(Olli.Pettay)
Attachment #364934 - Flags: review?(Olli.Pettay) → review+
pushed to m-c: http://hg.mozilla.org/mozilla-central/rev/d48c1c6c820b
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.