This test touches the network to load a Flash file: <http://mxr.mozilla.org/mozilla-central/source/layout/generic/crashtests/508908-1.html?force=1#22>. It happened today that there were some DNS issues on zombo.com, which caused the crashtest suite to fail to unload. I will file another bug about why this happened in the first place, but I'm disabling this test for now, to be able to reopen the tree.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b8
I filed bug 616088 for the underlying issue.
There's no bug on fixing and re-enabling the test, is there? Reopening to track this properly.
Assignee: ehsan → nobody
Severity: blocker → normal
Status: RESOLVED → REOPENED
Depends on: 616088
Resolution: FIXED → ---
Whiteboard: [test disabled]
Target Milestone: mozilla2.0b8 → ---
Actually, this probably doesn't need bug 616088, it looks like the test just needs to use a local rather than a remote resource.
No longer depends on: 616088
Ouch. Thanks for tracking that down! I can't believe we still have tests that hit the network. :-/
Sorry about that!!!!!!
All we need to do to reenable the test is to replace <embed src="http://zombo.com/inrozxa.swf"> with <embed type="application/x-test">.
Assignee: nobody → roc
We also need to do that on 1.9.2 and 1.9.1, where we're still merrily hitting zombo.com
Err, 1.9.2, since the test isn't on 1.9.1.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b11
And back out again in http://hg.mozilla.org/releases/mozilla-1.9.2/rev/e9231477e05b since unreasonable though this is, bug 629851 happened on all three platforms, and I didn't have a lot of choices other than to back out a crashtest change to see if that will fix a failure in a mochitest. Shrug.
And back in again in http://hg.mozilla.org/releases/mozilla-1.9.2/rev/caf45231174c, since it wasn't actually at fault.
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.
You need to log in before you can comment on or make changes to this bug.