Hi,
I just ran -apollo successfully on the VM. The initial run reports
1055 passing and 68 failing tests. The -failures run reports 0 passing
and 0 failures, so something is wrong there...
Now moving on to the -mobile tests...
EdB
On Wed, Jun 19, 2013 at 10:01 PM, Alex Harui aha...@adobe.com
Hi,
I just ran -apollo successfully on the VM. The initial run reports
1055 passing and 68 failing tests.
What version of AIR out of interest?
Justin
3.7, I think... how can I be sure? I looked at the 'airsdk.xml' in
AIR_HOME and that has airSdk
xmlns=http://ns.adobe.com/air/sdk/3.7;
EdB
On Thu, Jun 20, 2013 at 11:52 AM, Justin Mclean
jus...@classsoftware.com wrote:
Hi,
I just ran -apollo successfully on the VM. The initial run reports
1055 passing and 68 failing tests. The -failures run reports 0 passing
and 0 failures, so something is wrong there...
Ah, it looks like what's wrong was me... I didn't put in '-apollo' on
the failures run. The full command for failures on the AIR tests is
now: sh ./mini_run.sh -apollo -failures
Ok, the -mobile target also runs now. I see 3932 passing and 18 failing tests.
Now I'll re-run the -apollo target to see if the changes to the
-failures command have a positive effect...
EdB
On Thu, Jun 20, 2013 at 12:26 PM, Erik de Bruin e...@ixsoftware.nl wrote:
1055 passing and 68 failing
Hi,
3.7, I think... how can I be sure? I looked at the 'airsdk.xml' in
AIR_HOME and that has airSdk xmlns=http://ns.adobe.com/air/sdk/3.7;
Sound right. Probably need to run the normal SDK tests with FP 11.7 as well.
Perhaps it would be good to alternate what version of FP the tests are using
If 11.7 is the new long term support version, why not move to that as
the default FP version for Apache Flex? Why stick with 11.1?
Also, I think we can squeeze 2 full runs of all three targets in a
day. I can set up two sets of tests (e.g. 11.7 and the latests and
greatest - currently the 11.8
Hi,
If 11.7 is the new long term support version, why not move to that as
the default FP version for Apache Flex? Why stick with 11.1?
We don't want to force people to use the very latest, many enterprises have
locked down systems and may not be able to move to FP 11.7.
And how about the AIR
Ok, having to pick two, would you rather run against 11.1 and 11.7
(both 'long term support') or against 11.1 and the latest and greatest
released version (currently 11.7, but soon 11.8)?
For AIR we'll always run against the most recent release (non-beta).
EdB
On Thu, Jun 20, 2013 at 1:42 PM,
Hi,
Ok, having to pick two, would you rather run against 11.1 and 11.7
(both 'long term support') or against 11.1 and the latest and greatest
released version (currently 11.7, but soon 11.8)?
+1 for 11.1 and 11.7 from me but other people may think differently.
Justin
Interesting...
Ran -apollo, this time got 1059 passing and 68 failing. Note the 4
'extra' passing results, while there are still 68 failing tests...
Where did those come from?
The -apollo -failures no works, but reports 0 passing and 52
failing... What happened to the remaining 16 failures?
I'm
OK, but a reminder that there will be lots of bitmap compare failures when
you switch to 11.7 and resolving them are not my favorite thing to do.
On 6/20/13 4:19 AM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
3.7, I think... how can I be sure? I looked at the 'airsdk.xml' in
AIR_HOME
On 6/20/13 5:04 AM, Erik de Bruin e...@ixsoftware.nl wrote:
Interesting...
Ran -apollo, this time got 1059 passing and 68 failing. Note the 4
'extra' passing results, while there are still 68 failing tests...
Where did those come from?
Sometimes a SWF just doesn't startup. I have no idea why.
On 6/20/13 3:26 AM, Erik de Bruin e...@ixsoftware.nl wrote:
1055 passing and 68 failing tests. The -failures run reports 0 passing
and 0 failures, so something is wrong there...
Ah, it looks like what's wrong was me... I didn't put in '-apollo' on
the failures run. The full command for
FWIW, I think the tests are still running in some earlier namespace.
On 6/20/13 2:56 AM, Erik de Bruin e...@ixsoftware.nl wrote:
3.7, I think... how can I be sure? I looked at the 'airsdk.xml' in
AIR_HOME and that has airSdk
xmlns=http://ns.adobe.com/air/sdk/3.7;
EdB
On Thu, Jun 20, 2013 at
And if we solve them... will there be as many failures when we go back
to 11.1? We were thinking we might run once a day against 11.1 and
once a day against 11.7...
EdB
On Thu, Jun 20, 2013 at 5:12 PM, Alex Harui aha...@adobe.com wrote:
OK, but a reminder that there will be lots of bitmap
See http://localhost:8080/job/flex-sdk_mustella/177/changes
Cool, we had a clean run!!!
Let the games begin ;-)
EdB
On Wed, Jun 19, 2013 at 11:01 AM, flex.muste...@gmail.com wrote:
See http://localhost:8080/job/flex-sdk_mustella/177/changes
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Hi,
Cool, we had a clean run!!!
What version of FP was being used? (Windows and 11.1)
And you'll probably hate me for bringing this up but did we run the mobile or
AIR tests?
Thanks,
Justin
11.1, indeed.
And I guess not on the AIR and mobile tests... what ant
targets/switches make that happen?
EdB
On Wed, Jun 19, 2013 at 11:41 AM, Justin Mclean jmcl...@apache.org wrote:
Hi,
Cool, we had a clean run!!!
What version of FP was being used? (Windows and 11.1)
And you'll
For AIR it should be ./mini_run.sh -apollo tests/apollo
For mobile you'll need to swap in a different local.properties before
running mini_run on the mobile directory. See the wiki page for how to
set that up.
-Alex
On 6/19/13 2:48 AM, Erik de Bruin e...@ixsoftware.nl wrote:
11.1, indeed.
Can you give me an indication how long a run of each type takes?
EdB
On Wednesday, June 19, 2013, Alex Harui wrote:
For AIR it should be ./mini_run.sh -apollo tests/apollo
For mobile you'll need to swap in a different local.properties before
running mini_run on the mobile directory. See
This is definitely a great milestone :-)
Om
On Jun 19, 2013 2:32 AM, Erik de Bruin e...@ixsoftware.nl wrote:
Cool, we had a clean run!!!
Let the games begin ;-)
EdB
On Wed, Jun 19, 2013 at 11:01 AM, flex.muste...@gmail.com wrote:
See
I just tried it on my Mac.
20 minutes for AIR.
82 minutes for mobile.
Add more for -failures runs if needed.
I got a lot of bitmap failures that I'm looking into now. Which reminded
me that if a check-in goes bad and generates a lot of bitmap failures that
slows things down (all the bad pngs
24 matches
Mail list logo
