Closed Bug 651040 Opened 13 years ago Closed 11 years ago

Intermittent mostly Android failure in svg/as-image/border-image-simple-1.html and border-image-simple-2.html

Categories

(Core :: SVG, defect)

ARM
Android
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [mobile_unittests])

Attachments

(2 files)

Attached file reftest log
http://tinderbox.mozilla.org/showlog.cgi?log=Mobile/1303188814.1303190418.25152.gz
Android Tegra 250 mozilla-central opt test reftest-2 on 2011/04/18 21:53:34
s: tegra-073

REFTEST TEST-START | http://10.250.48.154:30073/tests/layout/reftests/svg/as-image/border-image-simple-1.html
REFTEST TEST-UNEXPECTED-FAIL | http://10.250.48.154:30073/tests/layout/reftests/svg/as-image/border-image-simple-1.html | image comparison (==) 
...
REFTEST number of differing pixels: 1164
REFTEST INFO | Saved log: START http://10.250.48.154:30073/tests/layout/reftests/svg/as-image/border-image-simple-1.html
REFTEST INFO | Saved log: [CONTENT] OnDocumentLoad triggering AfterOnLoadScripts
REFTEST INFO | Saved log: Initializing canvas snapshot
REFTEST INFO | Saved log: DoDrawWindow 0,0,800,1000
REFTEST INFO | Saved log: [CONTENT] RecordResult fired
REFTEST INFO | Saved log: RecordResult fired
REFTEST INFO | Saved log: RecordResult fired
Looks like the testcase has a 93px by 93px lime box, while the reference case has a 100px by 100px lime box.
Summary: Intermittent Android failure in svg/as-image/border-image-simple-1.html → Intermittent Android failure in svg/as-image/border-image-simple-1.html and border-image-simple-2.html
Summary: Intermittent Android failure in svg/as-image/border-image-simple-1.html and border-image-simple-2.html → Intermittent mostly Android failure in svg/as-image/border-image-simple-1.html and border-image-simple-2.html
Note: In recent border-image-simple-1.html logs (at least in comment 26 & comment 28), the reference-case data URIs are interrupted by a bunch of "before 389120, after 389120, break 05900000" text.  Not sure what that's about.

That's unrelated to the failure, though -- after snipping out that text, reftest-analyzer shows that the failure looks as described in comment 1.
It's about driving me crazy by shoving the GC from httpd.js (which, if I understand the setup for Android tests correctly, isn't even running on the same machine that's running the tests) into the log.
Whiteboard: [orange][mobile_unittests] → [mobile_unittests]
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: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: