Closed Bug 868892 Opened 12 years ago Closed 2 years ago

Bug 868556 caused failures in two webgl-color-alpha-test.html tests

Categories

(Core :: Graphics, defect)

ARM
Gonk (Firefox OS)
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [leave open])

Because there's basically no upper limit on the size of our clownshoes, after bug 868556 landed causing bustage in the reftest hunk I'd just unhidden, got backed out, then relanded annotating that reftest as failing, I noticed that it also caused two failures in the other hidden reftest hunk, the one that remains hidden. https://tbpl.mozilla.org/php/getParsedLog.php?id=22609952&tree=Mozilla-Inbound b2g_ics_armv7a_gecko_emulator mozilla-inbound opt test reftest-6 on 2013-05-05 07:21:12 PDT for push 39c44b2b1ef5 slave: talos-r3-fed-044 07:29:48 INFO - REFTEST TEST-UNEXPECTED-FAIL | http://10.0.2.2:8888/tests/content/canvas/test/reftest/webgl-color-alpha-test.html?colorVal=0.0&alphaVal=1.0&nogl | image comparison (==), max difference: 255, number of differing pixels: 65536 07:29:56 INFO - REFTEST TEST-UNEXPECTED-FAIL | http://10.0.2.2:8888/tests/content/canvas/test/reftest/webgl-color-alpha-test.html?colorVal=0.0&alphaVal=1.0 | image comparison (==), max difference: 255, number of differing pixels: 65536
Whiteboard: [leave open]
Thanks for handling this rather than backing me out again. Given comment 1, does this need more action? Why [leave open]?
My theory was that failing wasn't a permanent mandatory condition, but a bug that should be fixed.
Oh, that does make sense. It is likely that that is the same bug as the reftest-1 failure, and that is being fixed in bug 869011.
Depends on: 869011
Phil, is this bug still valid?
Flags: needinfo?(philringnalda)
No idea, I haven't looked at or spoken to anyone about b2g tests since they became tier-3, to know whether or not we still run them.
Flags: needinfo?(philringnalda)
Severity: normal → S3

Closing old B2G bugs

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.