Last modified: 2014-09-11 19:21:13 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 T71013, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69013 - Flow browser tests consistently fail with Timeout::Error (Timeout::Error)
Flow browser tests consistently fail with Timeout::Error (Timeout::Error)
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Quality Assurance (Other open bugs)
wmf-deployment
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: hhvm
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-01 17:17 UTC by Jon
Modified: 2014-09-11 19:21 UTC (History)
7 users (show)

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


Attachments

Description Jon 2014-08-01 17:17:43 UTC
Flow tests have been failing since build 112 mostly due to timeout errors

(See the descriptions I've added on
https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flow-en.wikipedia.beta.wmflabs.org-linux-firefox-sauce/
)

Do we know what's causing these? Any idea when/how we can resolve them?
Comment 1 Chris McMahon 2014-08-01 17:25:30 UTC
In a nutshell, HHVM is causing an issue for apaches.  See Ori's message to the QA list today: http://lists.wikimedia.org/pipermail/qa/2014-August/001817.html
Comment 2 Greg Grossmeier 2014-08-01 17:27:53 UTC
Chris's response to that post from Ori is probably right on track.
Comment 3 Antoine "hashar" Musso (WMF) 2014-08-19 14:20:02 UTC
+hiphop

Moving to Quality Assurance component which has the browser tests gurus :]
Comment 4 spage 2014-09-11 19:21:13 UTC
We haven't seen this error in Flow tests for several weeks, so declaring fixed.

(Nowadays our beta labs issue is Bug 68125 - browser tests failing with "getaddrinfo: Name or service not known (SocketError) )

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links