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 going to combine what I have and do a full run for 'main', 'apollo' and 'mobile' combined. That'll take the next 12 hours or so ;-) EdB On Thu, Jun 20, 2013 at 11:23 AM, Erik de Bruin <e...@ixsoftware.nl> 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... > > Now moving on to the "-mobile" tests... > > EdB > > > > On Wed, Jun 19, 2013 at 10:01 PM, Alex Harui <aha...@adobe.com> wrote: >> I forgot we added a -mobile option to mini_run.sh. You have to set up a >> local.properties as specified in the wiki except but leave adl_extras and >> run_mobile_tests and use_apollo commented out. They will get set by the >> -mobile option. >> >> On 6/19/13 12:49 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >> >>>> 20 minutes for AIR. >>>> 82 minutes for mobile. >>>> Add more for -failures runs if needed. >>> >>>Ok, I'll add these 2 runs to jenkins.sh. Might be a good idea to keep >>>the 'failures.txt' of each completed set (regular + -failures)? >> I suppose, or you could just bail at whatever run first produces failures >> that a -failures run won't clean up. The -failures run must also have the >> -apollo or -mobile option. >> >>> >>>> 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? >>> >>>I don't think Jenkins will stop one job just to start it again because >>>of a schedule... But I'll read up on it. The current run is 9 hrs, so >>>adding 1.5 hrs still leaves us with plenty of room on 'reasonably >>>clean' runs, right? >>> >>>EdB >>> >>> >>> >>>-- >>>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 -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
