Closed
Bug 1042534
Opened 10 years ago
Closed 10 years ago
Failing test, TEST-UNEXPECTED-FAIL | /builds/slave/test/gaia/apps/verticalhome/test/marionette/search_test.js | Vertical - Search General walkthrough
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kgrandon, Unassigned)
References
Details
(Keywords: intermittent-failure)
Attachments
(1 file)
Seems like a possible gecko regression: https://tbpl.mozilla.org/php/getParsedLog.php?id=44407720&tree=B2g-Inbound
Reporter | ||
Updated•10 years ago
|
Keywords: intermittent-failure
Reporter | ||
Comment 1•10 years ago
|
||
This test started perma-failing today due to some gecko changes. I'm not sure if there's *real* breakage, but disabling for now while we investigate: https://github.com/mozilla-b2g/gaia/commit/468e77e16b5a077cd2f7918a8ce33bffdb25ffe9
Keywords: leave-open
Comment 2•10 years ago
|
||
Given the dependency on bug 1015474 (which was mostly changing the default "min-width" / "min-height" behavior for flex items), it's likely that the problem can be solved by adding "min-width:0" or "min-height:0" to a particular element.
Updated•10 years ago
|
Blocks: minsizeauto-fallout
Comment 3•10 years ago
|
||
(I'm marking this as blocking bug 1043520 instead of bug 1015474. Per bug 1043520 comment 2, I'm using that bug to track issues with content caused by the introduction of "min-width:auto"/"min-height:auto". (as opposed to actual bugs in the feature, which should block bug 1015474). I'm betting this is the former case, though we can adjust the blocking field as-necessary if I'm proven wrong.)
No longer blocks: 1015474
Reporter | ||
Comment 4•10 years ago
|
||
Attachment #8462629 -
Flags: review?(etienne)
Updated•10 years ago
|
Attachment #8462629 -
Flags: review?(etienne) → review+
Reporter | ||
Comment 5•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 7•7 years ago
|
||
Removing leave-open keyword from resolved bugs, per :sylvestre.
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•