Back on 10.3, I did some adjustments: setting
DEFAULT_NUM_COLOR_VARIANCES:int = 255 and the default value of
ignoreMaxColorVariance to true in the CompareBitmap class, I've been able to
reduce the number of failed tests to 1 (only
text_long_property_Label_Spark.png doesn't pass and I can't get why because
whatever the number of color variance I allowed, it always said they exeeded
by 4).
Well, anyway, it's not a solution, that's only to hide the failures, if we
go anyway that way, what I'm not sure, we'll need to have a conditional
compilation to say we're in a lower version of the player and the tests
should be more tolerants.
What do you think ?
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Saturday, October 27, 2012 11:04 AM
To: flex-dev@incubator.apache.org
Subject: Re: About Flex runtime
Forget my last post please, env.properties hasn't been saved.
The actual result for Label is :
[java] =====================================================
[java] Failed:
[java] =====================================================
[java]
[java]
[java] =====================================================
[java] Passes: 255
[java] Fails: 0
[java] =====================================================
[java]
[java]
[java] waited 2000
[java] ClobberProcess, it was already null
[java] Wrote summary to results.txt
[java] Wrote failures to failures.txt
call_runners:
run:
BUILD SUCCESSFUL
Total time: 1 minute 31 seconds
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Saturday, October 27, 2012 10:52 AM
To: flex-dev@incubator.apache.org
Subject: Re: About Flex runtime
Just did the tests on Label against the 11.4 and had the same failures than
the 10.3
-----Message d'origine-----
From: Justin Mclean
Sent: Saturday, October 27, 2012 2:19 AM
To: flex-dev@incubator.apache.org
Subject: Re: About Flex runtime
Hi,
Looks like 10.3 chooses antialiasing differently than 11.1.
Any idea about more recent versions greater than 11.1? I guess that's
probably more important than getting all test to pass in 10.3.
Thanks,
Justin
