FaviconFetcherTests random failures in silo builds
Bug #1498539 reported by
Olivier Tilloy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtbase-opensource-src (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
webbrowser-app (Ubuntu) |
Fix Released
|
Critical
|
Olivier Tilloy |
Bug Description
Since yesterday (2015-09-21), FaviconFetcherTests started failing at random in silo builds (not failing all the time, but in about 50% of the builds).
Since it has been happening in several silos, it’s very unlikely that it’s a change in webbrowser-app itself that triggered the failure. It’s more likely a change somewhere else in the stack that triggered a bug that was already there.
Related branches
lp:~osomon/webbrowser-app/shouldCancelRequests-handle-errors
- Ugo Riboni (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 84 lines (+22/-13)1 file modifiedtests/unittests/favicon-fetcher/tst_FaviconFetcherTests.cpp (+22/-13)
Changed in webbrowser-app (Ubuntu): | |
status: | Triaged → In Progress |
To post a comment you must log in.
It took me a while to manage to reproduce locally, but here it is, the failing test is shouldCancelReq uests, and the failure message is:
'serverSpy- >wait() ' returned FALSE. ()
Full XML output for the failing test is:
<testcase result="fail" name="shouldCan celRequests" > "QIODevice: :write: device not open" type="qwarn" --> "' serverSpy& #x002D; >wait( )' returned FALSE. ()" result="fail"/>
<!-- message=
<failure message=
</testcase>