Closed
Bug 597636
Opened 14 years ago
Closed 7 years ago
mochitest is really slow when my DNS server is flaky
Categories
(Testing :: Mochitest, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dbaron, Unassigned)
References
Details
I've noticed a few times that when my DNS server is flaky (at least I'm pretty sure that's what it is, because when I switch to VPN, which changes my DNS server, it gets better), that mochitest is very slow to start up.
I wonder if this dependency on real DNS in order to start could be responsible for some of our random orange.
In particular, I just ran "make mochitest-plain TEST_PATH=layout/style/test/test_transitions_per_property.html" with an nsHostResolver:5 NSPR log, and ran tail -f on that NSPR log as it was generated. What I saw was:
-1351703008[fa7ab0]: nsHostResolver::ResolveHost [host=mochi.test]
-1351703008[fa7ab0]: DNS Thread Counters: total=1 any-live=0 idle=0 pending=1
-1051719920[26f3b80]: nsHostResolver::ThreadFunc entering
-1051719920[26f3b80]: resolving mochi.test ...
-1351703008[fa7ab0]: nsHostResolver::ResolveHost [host=mochi.test]
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=127.0.0.1]
[ a 2-4 second pause ]
-1351703008[fa7ab0]: nsHostResolver::ResolveHost [host=fxfeeds.mozilla.com]
-1351703008[fa7ab0]: DNS Thread Counters: total=2 any-live=0 idle=0 pending=1
-1032841456[281f060]: nsHostResolver::ThreadFunc entering
-1032841456[281f060]: resolving fxfeeds.mozilla.com ...
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=fxfeeds.mozilla.com]
-1032841456[281f060]: lookup complete for fxfeeds.mozilla.com ...
-1351703008[fa7ab0]: nsHostResolver::ResolveHost [host=fxfeeds.mozilla.com]
-1351703008[fa7ab0]: using cached record
-1351703008[fa7ab0]: nsHostResolver::ResolveHost [host=newsrss.bbc.co.uk]
-1351703008[fa7ab0]: DNS Thread Counters: total=2 any-live=0 idle=1 pending=1
-1032841456[281f060]: resolving newsrss.bbc.co.uk ...
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=newsrss.bbc.co.uk]
-1032841456[281f060]: lookup complete for newsrss.bbc.co.uk ...
-1351703008[fa7ab0]: nsHostResolver::ResolveHost [host=feeds.bbci.co.uk]
-1351703008[fa7ab0]: DNS Thread Counters: total=2 any-live=0 idle=1 pending=1
-1032841456[281f060]: resolving feeds.bbci.co.uk ...
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=feeds.bbci.co.uk]
-1032841456[281f060]: lookup complete for feeds.bbci.co.uk ...
[ a 30-60 second pause ]
-1051719920[26f3b80]: calling res_ninit
[ a 30-60 second pause ]
-1051719920[26f3b80]: lookup complete for mochi.test ...
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=127.0.0.1]
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=127.0.0.1]
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=127.0.0.1]
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=127.0.0.1]
-1211328752[126cf50]: nsHostResolver::ResolveHost [host=127.0.0.1]
Comment 1•14 years ago
|
||
We should probably add a pref to disable livemark updates and set it in the testing profile (none of the current livemark prefs are suitable for this).
Comment 2•7 years ago
|
||
Mass closing mochitest bugs that haven't had activity in the past 5 years. Please re-open or file a new bug with modern context if this is still relevant.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•