Current time: 12-15-2017, 01:15 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Nexus 5 tester with stale DNS override
03-31-2017, 05:34 AM
Post: #1
Nexus 5 tester with stale DNS override
The tester Nexus5_3-192.168.0.173 seems to have a stale DNS override from a previous test. See https://www.webpagetest.org/result/17033...view_step1
Find all posts by this user
Quote this message in a reply
03-31-2017, 11:29 PM
Post: #2
RE: Nexus 5 tester with stale DNS override
Do you just mean that the DNS time was zero or is there something that makes you think a previous override carried forward?

The problem of it recording zero could be that either the android DNS cache isn't getting flushed well or that Chrome didn't record the DNS time in the netlog for some reason.
Visit this user's website Find all posts by this user
Quote this message in a reply
04-01-2017, 05:37 AM (This post was last modified: 04-01-2017 05:38 AM by lawnsea.)
Post: #3
RE: Nexus 5 tester with stale DNS override
(03-31-2017 11:29 PM)pmeenan Wrote:  Do you just mean that the DNS time was zero or is there something that makes you think a previous override carried forward?

The problem of it recording zero could be that either the android DNS cache isn't getting flushed well or that Chrome didn't record the DNS time in the netlog for some reason.

No, a previous override carried forward. Compare runs #1 and #2: https://www.webpagetest.org/result/17033...0ec12bbe/. The .173 tester has a stale DNS override to Yotta's reverse proxy.
Find all posts by this user
Quote this message in a reply
04-01-2017, 06:27 AM
Post: #4
RE: Nexus 5 tester with stale DNS override
Thanks. It was a bug in the new agents launched Friday where any command-line or host rules changes would accumulate for the time the agent was running (they run for an hour before exiting and checking for updates).

Code is fixed now and the agents will pick it up over the next hour. All of the Nexus 5's have been updated.

Here's the fix: https://github.com/WPO-Foundation/wptage...b3318a877e
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)