I have looked for the different baseline bitmaps to compare:

integration\baselines\Skin_test_1@win_240ppi.png
integration\baselines\Change_skin_at_runtime@win_240ppi.png
integration\baselines\Callout_skin @win_240ppi.png
etc.

And the bitmaps are all missing from 

mustella\tests\mobile\SplitViewNavigator\integration\baselines

Could it be the reason for the failure ?

NB: if you already found out, please ignore my email ...

Maurice 

-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] 
Envoyé : jeudi 10 octobre 2013 00:08
À : dev@flex.apache.org
Objet : RE: Build failed in Jenkins: flex-sdk_mustella #460

Hi, I have run the SplitNavigatorView and also had the 6 fails:

   [java] mobile/SplitViewNavigator/integration/SplitViewNavigator_integration 
Skin_test_1 Failed CompareBitmap(body:step 4)  compare returned-3 
     [java] 
mobile/SplitViewNavigator/integration/SplitViewNavigator_integration 
Change_skin_at_runtime Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] 
mobile/SplitViewNavigator/integration/SplitViewNavigator_integration 
Callout_skin Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] mobile/SplitViewNavigator/methods/SplitViewNavigator_methods 
showFirstViewNavigatorInCallout_multiple_navigators Failed 
CompareBitmap(body:step 3)  compare returned-3 
     [java] mobile/SplitViewNavigator/methods/SplitViewNavigator_methods 
showFirstViewNavigatorInCallout_one_navigator Failed CompareBitmap(body:step 3) 
 compare returned-3 
     [java] mobile/SplitViewNavigator/integration/SplitViewNavigator_tabbedApp 
TabbedApp_callout_open Failed CompareBitmap(body:step 3)  compare returned-3 
  
Is it possible that it's related to the Callout merge ?

Where do I find the baseline bitmaps for these failures, so that I can see 
where the differences are ?

Thanks 

Maurice 

-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mercredi 9 octobre 2013 20:04
À : dev@flex.apache.org
Objet : RE: Build failed in Jenkins: flex-sdk_mustella #460

Ah sorry.
That what happens when you don't read the whole thread :-).

Maurice 

-----Message d'origine-----
De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash 
Muppirala Envoyé : mercredi 9 octobre 2013 20:01 À : dev@flex.apache.org Objet 
: Re: Build failed in Jenkins: flex-sdk_mustella #460

On Wed, Oct 9, 2013 at 10:58 AM, Maurice Amsellem < 
maurice.amsel...@systar.com> wrote:

> Hi, when browsing the history on develop branch, last change on 
> SplitViewNavigator is back from 4/26/2013 and it's really a minor change.
> Did I miss something ?
>
>
Alex mentioned that it could be related to the supportClasses vs.
supportClazzes change.

Thanks,
Om


> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mercredi 9 
> octobre 2013 19:33 À : dev@flex.apache.org Objet : Re: Build failed in
> Jenkins: flex-sdk_mustella #460
>
> Develop branch, of course.
>
> And the current status is that both 'main' and 'mobile' have failing 
> tests. Where the 'main' failures seem mostly related to FTETextField 
> and the failures for 'mobile' center around SplitViewNavigator.
>
> The VM runs on Windows Server 2008. The three Mustella test suites run 
> on
> 4 versions of the FP and 2 of AIR consecutively: 11.1, 11.7, 11.8 and 
> 11.9;
> 3.8 and 3.9.
>
> Each of these failures started after a commit to the component in 
> question, IIRC. I don't have time in the next 12 hours to look at any 
> of this in more detail, so feel free to browse the VM ;-)
>
> EdB
>
>
>
> On Wed, Oct 9, 2013 at 8:37 AM, Justin Mclean 
> <jus...@classsoftware.com>
> wrote:
> > Hi,
> >
> > Is the testing VM using the master or develop branch of TLF?
> >
> > Justin
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Reply via email to