Closed Bug 629851 Opened 9 years ago Closed 9 years ago

Permanent failures in test_bug481335.xhtml on 1.9.2 | Should be visited now - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)", Should still be visited after setting pathname to its existing value, Should be vi

Categories

(Core :: DOM: Core & HTML, defect)

1.9.2 Branch
x86
All
defect
Not set

Tracking

()

RESOLVED FIXED
Tracking Status
status1.9.2 --- .17-fixed

People

(Reporter: philor, Assigned: philor)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.6/1296272836.1296274719.2324.gz
Linux mozilla-1.9.2 test mochitests on 2011/01/28 19:47:16
s: linux-ix-slave41

39527 INFO TEST-PASS | /tests/content/html/content/test/test_bug481335.xhtml | Should be unvisited now - "rgb(0, 0, 238)" should equal "rgb(0, 0, 238)"
39528 ERROR TEST-UNEXPECTED-FAIL | /tests/content/html/content/test/test_bug481335.xhtml | Should be visited now - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)"
39529 ERROR TEST-UNEXPECTED-FAIL | /tests/content/html/content/test/test_bug481335.xhtml | Should still be visited after setting pathname to its existing value - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)"
aaa39530 INFO TEST-PASS | /tests/content/html/content/test/test_bug481335.xhtml | Should not be visited after changing pathname - "rgb(0, 0, 238)" should not equal "rgb(85, 26, 139)"
39531 INFO TEST-PASS | /tests/content/html/content/test/test_bug481335.xhtml | Should not be visited after setting unvisited pathname to existing value - "rgb(0, 0, 238)" should not equal "rgb(85, 26, 139)"
39532 ERROR TEST-UNEXPECTED-FAIL | /tests/content/html/content/test/test_bug481335.xhtml | Should be visited now after third load - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)"
Seems a bit suspicious that I apparently caused this by landing http://hg.mozilla.org/releases/mozilla-1.9.2/rev/b4529434e248, which changed a crashtest.
OS: Linux → All
Attached patch FixSplinter Review
Bad word. Bad word bad word bad word.

Not long after I backed out http://hg.mozilla.org/releases/mozilla-1.9.2/rev/b4529434e248 despite there being no way it could have caused this, I noticed that although we proxy www.example.com on the trunk, where this is not failing, we do not proxy it on 1.9.2. Then I loaded http://www.example.com/, and thanks to some brilliant work by IANA, found myself redirected to http://www.iana.org/domains/example/.

The test worked fine on 1.9.2, though it was loading the actual www.example.com, right up until it stopped loading that, and started loading something entirely different.
Assignee: nobody → philringnalda
Status: NEW → ASSIGNED
Attachment #508082 - Flags: review?(jwalden+bmo)
Blocks: 626999
Summary: Intermittent failures in test_bug481335.xhtml | Should be visited now - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)", Should still be visited after setting pathname to its existing value - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)" Should be vi → Permanent failures in test_bug481335.xhtml on 1.9.2 | Should be visited now - "rgb(0, 0, 238)" should equal "rgb(85, 26, 139)", Should still be visited after setting pathname to its existing value, Should be vi
Landed http://hg.mozilla.org/releases/mozilla-1.9.2/rev/ea2afbe439c3 as a bustage fix, though I think we're better off having both the test and server-locations being the same on the trunk and 1.9.2.
Comment on attachment 508082 [details] [diff] [review]
Fix

The real-world example.com redirects?  DO NOT WANT.
Attachment #508082 - Flags: review?(jwalden+bmo) → review+
philor: are you leaving this open for a better fix?
Attachment 508082 [details] [diff] is the better fix, but I also need to revert my workaround from comment 11 when I land it, so that we'll actually be using it.
The "3.6.15" we're releasing today does not fix this bug, the release containing this bug fix has been renamed to "3.6.16" and the bugzilla flags will be updated to reflect that soon. Today's release is a re-release of 3.6.14 plus a fix for a bug that prevented many Java applets from starting up.
Whiteboard: [orange]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.