If the exact width/height could be found for each test then these could
be marked in a manifest (theoretically, not speaking to the existing
reftest manifest format per se). Then reftest could be modified to take
a (e.g.) --resoltuion 400x400 argument and the test runner passing over
any test that exceeds either dimension.
Just a thought. Not sure how feasible this is.
On 08/28/2012 09:52 AM, Andrew Halberstadt wrote:
== The Problem ==
Reftests currently assume a window size of 800x1000. This is not
possible on mobile devices, and using this resolution on tegras and
pandas consumes too much memory and results in many timeouts and
random-failures.
Changing the resolution to something like 400x400 is very stable and
only results in a handful of failures. The problem is it's difficult
to figure out how many tests are false positives as a result of lost
coverage.
See also: https://bugzilla.mozilla.org/show_bug.cgi?id=737961
== Possible Solutions ==
* Somehow figure out the exact pixel width/height required by each
test and re-write the ones that are over the new target resolution
* Scroll the contentView and use multiple drawWindow calls to stitch
the canvases together piece by piece
* Disable the DRAW_WIDGET_LAYERS flag so content is rendered off
screen (I'm under the impression this is not a valid solution)
* ?
Things to keep in mind:
* Needed for fennec and b2g (must work oop)
* Some of the tests are shared (apparently?) outside of mozilla
== Feedback ==
I'm looking for feedback on the best way to move forward. Also, does
anyone have any opinions on what the new target resolution should be?
Andrew
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
