Closed Bug 785809 Opened 7 years ago Closed 7 years ago

Intermittent test_value_cloning.html | computed value should be nonempty for border-top: -moz-initial - didn't expect , but got it, | computed values should match when cloning border-top: -moz-initial - got rgb(0, 0, 0) ; none ;

Categories

(Core :: CSS Parsing and Computation, defect)

x86
Linux
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

+++ This bug was initially created as a clone of Bug #775944 +++

https://tbpl.mozilla.org/php/getParsedLog.php?id=14737543&tree=Mozilla-Inbound
Rev3 Fedora 12 mozilla-inbound opt test mochitests-4/5 on 2012-08-26 23:49:00 PDT for push a684417d8536
slave: talos-r3-fed-008

116482 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_value_cloning.html | computed value should be nonempty for border-top: -moz-initial - didn't expect , but got it
...
119666 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_value_cloning.html | computed values should match when cloning border-top: -moz-initial - got rgb(0, 0, 0) ; none ; 0px, expected
Summary: Intermittent test_value_cloning.html | test_value_cloning.html | computed value should be nonempty for border-top: -moz-initial - didn't expect , but got it, | computed values should match when cloning border-top: -moz-initial - got rgb(0, 0, 0) ; none ; → Intermittent test_value_cloning.html | computed value should be nonempty for border-top: -moz-initial - didn't expect , but got it, | computed values should match when cloning border-top: -moz-initial - got rgb(0, 0, 0) ; none ;
Whiteboard: [orange]
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of:
{random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open}

There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.