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 have to be written to disk). Is there any way to set up jenkins to wait N minutes after a job completes before starting the next job? What would happen if we run every 12 hours but sometimes a job doesn't complete in those 12 hours? -Alex On 6/19/13 7:28 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >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 the wiki page for how to >> set that up. >> >> -Alex >> >> On 6/19/13 2:48 AM, "Erik de Bruin" <e...@ixsoftware.nl <javascript:;>> >> wrote: >> >> >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<javascript:;> >> > >> >wrote: >> >> 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 >> > >> > >> > >> >-- >> >Ix Multimedia Software >> > >> >Jan Luykenstraat 27 >> >3521 VB Utrecht >> > >> >T. 06-51952295 >> >I. www.ixsoftware.nl >> >> > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
