Last modified: 2014-10-19 17:44:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T70125, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 68125 - browser tests failing with "getaddrinfo: Name or service not known (SocketError)"
browser tests failing with "getaddrinfo: Name or service not known (SocketErr...
Status: REOPENED
Product: Wikimedia
Classification: Unclassified
Quality Assurance (Other open bugs)
unspecified
All All
: Low major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 60338
  Show dependency tree / graph
 
Reported: 2014-07-16 21:30 UTC by spage
Modified: 2014-10-19 17:44 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description spage 2014-07-16 21:30:15 UTC 
This was mentioned on the "[QA] Failing MobileFrontend browser tests" thread in July. I have seen a few more  "getaddrinfo: Name or service not known (SocketError)" errors with Flow browser tests, and then today we got four of them. :-(

See https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/65/

All three tests failures in https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/65/ at Jul 16, 2014 6:26:46 PM (UTC?) were with this error.

15 minutes earlier, https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/72/ also failed with "getaddrinfo: Name or service not known (SocketError)". The other test failure was an action that took longer than 5 seconds to complete.
Comment 2 Chris McMahon 2014-07-16 21:35:21 UTC 
Seems to be a 90 second timeout for a Flow job as well, but without the big red error message at the top of the Sauce page: https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/72/testReport/junit/(root)/Topic%20collapsing/Topics_only_view/
Comment 3 Chris McMahon 2014-07-25 15:02:39 UTC 
This is very likely fixed with
Comment 4 spage 2014-09-08 06:54:28 UTC 
(In reply to Chris McMahon from comment #3)
> This is very likely fixed with

"fixed with what" ? HHVM improvements?

Anyway, this remains a problem. From e-mail to qa mailing list:
>>>
Echo and Flow tests were all green Saturday Sept 6 for the first time \o/

But then 4 out of 6 Flow test runs today (
  Sep 7, 2014 8:33:11 PM
  Sep 7, 2014 6:51:45 PM    
  Sep 7, 2014 6:13:05 PM
  Sep 7, 2014 3:54:07 AM
UTC times I think)
<<<
Tthere was another getaddrinfo failure Sep 8, 2014 3:45:56 AM, see 
<https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-chrome-sauce/185/>
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links