Filed by: hskupin [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=248473367&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/fijA1hBrRsidezlkkSchbA/runs/0/artifacts/public/logs/live_backing.log

undefined

This was regressed by bug 1546880. As it looks like this only happens in some cases for the tp5 sites.

Joel, do you have an idea where the call to ping.ie.sogou.com is made? There is nothing in the tree, which references this host.

odd, I suspect this is a website inside of tp5- probably an edge case that didn't exist before. Unfortunately we are not at a point to remove tp5 from the running as we don't have a way to measure responsiveness of the browser anywhere else- once we have that in tp6 tests or in other scenarios, tp5 could be shut down.

the way to fix this would be to get the tp5 pageset, find the call to ping.ie.sogou.com and remove it. Then repackage tp5n.zip, upload it, and the problem would be solved.

Joel, could you or someone from SV do that please? I'm moving back to my team, and won't really have the time for that. Thanks!

:davehunt, can you find someone on your team to work on this?

(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #6)

:davehunt, can you find someone on your team to work on this?

Yes, thanks for the prompt. Bebe could you get someone to look into this?

(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #4)

the way to fix this would be to get the tp5 pageset, find the call to ping.ie.sogou.com and remove it. Then repackage tp5n.zip, upload it, and the problem would be solved.

Not verry familiar with tp5 tests
how can we disable the that call?

From digging through the tp5n code I have found some httpdisabled links. Is that the way?

httpdisabled is the way that wget fixed the problem, that is a safe way to do it. otherwise, I often remove the link that it is making, or make it 127.0.0.1 instead.

Keep in mind you might need to sear for sogou.com and then filter for ping- it might be dynamically built up.

try build with the new recordings file:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=a7b4e56b2332c42998e825219ad1ef5d4fc0a072

Florin, thank you for taking this up. Mind showing what the exact change is which was necessary here?

Not sure how to highlight this...

I searched the archive all the links to ping.ie.sogou.com and added the httpdisabled

This is the solution used in the past to fix this issue and try build proves that it works

https://hg.mozilla.org/mozilla-central/rev/ec56085daaf1

Last push time in the intermittent is 2019-06-05 09:52:25

Let's see if we have any intermittent after that time

(In reply to Florin Strugariu [:Bebe] from comment #19)

Last push time in the intermittent is 2019-06-05 09:52:25

Let's see if we have any intermittent after that time

Those were just failures from before the landing on June 5th. So it's all fine.

This seems to be permafailing on autoland:
https://treeherder.mozilla.org/#/jobs?repo=autoland&searchStr=linux%2Cx64%2Copt%2Ctalos%2Cperformance%2Ctests%2Ctest-linux64%2Fopt-talos-tabswitch-e10s%2Ct%28tabswitch%29&tochange=8ba01fc4f7e017b5ef1754d435c911c4e3847ef8&fromchange=6153e6bb58e1fb7015c89722eaa1830850e165f5&selectedJob=252215477

And started permafailing on central after the changes from bug 1529345 were merged to central:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&searchStr=%28tabswitch%29&fromchange=19cf79b6f07d4c5c93d29d6b73d40df4497db657&tochange=40c99f4752f968db32f189243b4432b18d1b3471&selectedJob=252170701

:whimboo can you, please, take a look?

Bogdan, it doesn't make sense to add more comments to a bug which is fixed. If there is some kind of new regression a new bug has to be filed. Please also note that this new failure is 127.0.0.1.woopra-ns.com and not ping.ie.sogou.com.

Bug 1559749 was created for the failures mentioned on comment 21. I don't think bug 1529345 is related to these failures, maybe Bug 1554724? Florin, could you try a patch for the new failures? Also please ignore the classifications made against this bug in the last two days. Thanks

Update: Logan's changes in 1529345 are not the ones which caused the regression: https://treeherder.mozilla.org/#/jobs?repo=try&revision=03b5005ab1a6f8aa13425e4a8d28103a40a8e639

As stated above this is related to Bug 1559749

The current bug is fixed.