RE: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Maurice Amsellem
issues are blocking, IMO, so it can wait... Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : vendredi 22 novembre 2013 20:32 À : dev@flex.apache.org; Erik de Bruin Cc : Mark Kessler; jmcl...@apache.org Objet : Re: Build failed in Jenkins: flex-sdk_must

Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Alex Harui
> >Excellent. > >Thanks Alex for the hint > >Maurice > >-Message d'origine- >De : Alex Harui [mailto:aha...@adobe.com] >Envoyé : vendredi 22 novembre 2013 19:42 >À : dev@flex.apache.org; Erik de Bruin >Cc : Mark Kessler; jmcl...@apache.org >Objet : R

RE: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Maurice Amsellem
jmcl...@apache.org Objet : Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382 The png.xml files can be sensitive to what else runs before it. Did you run the entire ActionBar folder? ./mini_run.sh -mobile tests/mobile/components/ActionBar/ If you still get a bad.png.xml, post it so I can se

Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Alex Harui
> >>>then run again the same test: >>>$ ./mini_run.sh -mobile >>>tests/mobile/components/ActionBar/styles/ActionBar_Styles.mxml >>> >>>The log says: >>>[echo] sdk.dir: C:/Program Files (x86)/Apache >>>Flex/Apache_Flex_SDK_

RE: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Maurice Amsellem
_Flex_SDK_411_GA >>... >>[echo] apollo_location is C:/Program Files (x86)/Apache >>Flex/Apache_Flex_SDK_411_GA >> >>WDYT? >> >>Maurice >> >>-Message d'origine- >>De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : vendredi

Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Alex Harui
411_GA >>... >>[echo] apollo_location is C:/Program Files (x86)/Apache >>Flex/Apache_Flex_SDK_411_GA >> >>WDYT? >> >>Maurice >> >>-Message d'origine- >>De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : vendredi 22 >>

RE: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Maurice Amsellem
27;origine- >De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : vendredi 22 >novembre 2013 16:11 À : Maurice Amsellem Cc : dev@flex.apache.org; Mark >Kessler; jmcl...@apache.org Objet : Re: Build failed in Jenkins: >flex-sdk_mustella-mobile #382 > >Well, my records show th

Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Alex Harui
are.nl] >Envoyé : vendredi 22 novembre 2013 16:11 >À : Maurice Amsellem >Cc : dev@flex.apache.org; Mark Kessler; jmcl...@apache.org >Objet : Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382 > >Well, my records show this test started failing on Nov. 18th. > >EdB >

RE: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Maurice Amsellem
rigine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : vendredi 22 novembre 2013 16:11 À : Maurice Amsellem Cc : dev@flex.apache.org; Mark Kessler; jmcl...@apache.org Objet : Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382 Well, my records show this test started failing on N

Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Erik de Bruin
-Message d'origine- > De : Erik de Bruin [mailto:e...@ixsoftware.nl] > Envoyé : vendredi 22 novembre 2013 15:36 > À : dev@flex.apache.org > Cc : Mark Kessler; jmcl...@apache.org; Maurice Amsellem > Objet : Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382 > >

RE: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Maurice Amsellem
rk Kessler; jmcl...@apache.org; Maurice Amsellem Objet : Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382 Hi, since the Mustella VM seems to have settled down now, I think we can confidently say this failure needs to be addressed - it is not an artifact of the build machine. Anyone? EdB

Re: Build failed in Jenkins: flex-sdk_mustella-mobile #382

2013-11-22 Thread Erik de Bruin
Hi, since the Mustella VM seems to have settled down now, I think we can confidently say this failure needs to be addressed - it is not an artifact of the build machine. Anyone? EdB On Fri, Nov 22, 2013 at 2:26 PM, wrote: > See