Re: iss...@flex.apache.org list now active
What about moving Mustella build fails to issues as well? On Thu, Jun 20, 2013 at 10:59 AM, Frédéric THOMAS webdoubl...@hotmail.comwrote: Works better, thanks -Message d'origine- From: Alex Harui Sent: Thursday, June 20, 2013 5:24 PM To: dev@flex.apache.org Subject: Re: iss...@flex.apache.org list now active Did you try to subscribe from the email alias that is mapped to your apache.org id? On 6/20/13 5:31 AM, Frédéric THOMAS webdoubl...@hotmail.com wrote: I had a Delivery Status Notification (Failure) after sending the confirmation, trying to go by issues-request@flex.apache.**orgissues-requ...@flex.apache.org was the same, what to do now ? -Fred -Message d'origine- From: Erik de Bruin Sent: Thursday, June 20, 2013 2:10 PM To: dev@flex.apache.org Subject: iss...@flex.apache.org list now active All, The iss...@flex.apache.org list has been created and is now active. All JIRA emails are sent to that list instead of dev@. All committers should subscribe to the new list! Please send an email to: issues-subscribe@flex.apache.**org issues-subscr...@flex.apache.org to start the process. All direct replies to emails from that list are sent to dev@ as well, so no discussion on any JIRA issue will be lost in yet another list :-) EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Mustella VM emails to 'issues'?
commits@ or issues@ I would say what is better but what is sure is it pollutes the dev list. Those 2 lists are followed as well by committers or at least PMCs, otherwise what do you thing about another list builds@ ? does it worth ? -Fred -Message d'origine- From: Alex Harui Sent: Friday, June 28, 2013 4:35 PM To: dev@flex.apache.org Subject: Re: Mustella VM emails to 'issues'? On 6/28/13 12:32 AM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, I was just wondering: would it be better if I have Jenkins send the Mustella run emails to 'issues@'? Wouldn't commits@ be better? The way it stands now, all three runs (main, AIR and mobile) have tests failing (even after -failures). This means that per full run, three emails will be sent... twice a day. That will put even Justin's JIRA email production to shame ;-) I think it will be cleaner if I direct those emails somewhere they don't interfere with the 'regular' discussions? I'll try to spend some time cleaning up the runs next week.
Re: Mustella VM emails to 'issues'?
I think commits@f.a.o would be the best place. Builds break because of bad commits (most of the times) Moreover an additional list (ex. builds@f.a.o) would be a bit of an overkill. Thanks, Om On Sat, Jun 29, 2013 at 12:16 AM, Frédéric THOMAS webdoubl...@hotmail.comwrote: commits@ or issues@ I would say what is better but what is sure is it pollutes the dev list. Those 2 lists are followed as well by committers or at least PMCs, otherwise what do you thing about another list builds@ ? does it worth ? -Fred -Message d'origine- From: Alex Harui Sent: Friday, June 28, 2013 4:35 PM To: dev@flex.apache.org Subject: Re: Mustella VM emails to 'issues'? On 6/28/13 12:32 AM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, I was just wondering: would it be better if I have Jenkins send the Mustella run emails to 'issues@'? Wouldn't commits@ be better? The way it stands now, all three runs (main, AIR and mobile) have tests failing (even after -failures). This means that per full run, three emails will be sent... twice a day. That will put even Justin's JIRA email production to shame ;-) I think it will be cleaner if I direct those emails somewhere they don't interfere with the 'regular' discussions? I'll try to spend some time cleaning up the runs next week.
Installer now supports nightly builds!
Thanks to Erik's fix for the MD5 checksum comparison issue, we now have support for installing nightly releases from the Apache build server. I fixed a couple of bugs and did some cosmetic changes. It looks like the Installer is ready for its next release. How is the Flex SDK release looking? Thanks, Om
Build failed in Jenkins: flex-sdk_mustella-air #10
See http://localhost:8080/job/flex-sdk_mustella-air/10/ -- [...truncated 7469 lines...] [java] FAIL: apollo/spark/components/Window/properties/window_properties_height_tests height_test4_windowedApplicationSkin [java] FAIL: apollo/spark/components/Window/properties/window_properties_height_tests height_test5_SparkChrome [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/properties/baselines/height_test7_SparkChrome.png.bad.png length: 1584 [java] FAIL: apollo/spark/components/Window/properties/window_properties_height_tests height_test5_windowedApplicationSkin [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/properties/baselines/height_test7_windowedApplicationSkin.png.bad.png length: 591 [java] FAIL: apollo/spark/components/Window/properties/window_properties_height_tests height_test6_SparkChrome [java] FAIL: apollo/spark/components/Window/properties/window_properties_height_tests height_test6_windowedApplicationSkin [java] FAIL: apollo/spark/components/Window/properties/window_properties_height_tests height_test7_SparkChrome [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/properties/baselines/status_test1_systemChrome.png.bad.png length: 1294 [java] FAIL: apollo/spark/components/Window/properties/window_properties_height_tests height_test7_windowedApplicationSkin [java] FAIL: apollo/spark/components/Window/properties/window_properties_status_systemchrome_tests status_test1_systemChrome [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/properties/baselines/status_test2_systemChrome.png.bad.png length: 319 [java] FAIL: apollo/spark/components/Window/properties/window_properties_status_systemchrome_tests status_test2_systemChrome [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/skin/baselines/titleBar_test1_SparkChrome.png.bad.png length: 847 [java] FAIL: apollo/spark/components/Window/skin/window_skin_titleBar_tests titleBar_test1_SparkChrome [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/skin/baselines/titleBar_test2_SparkChrome.png.bad.png length: 980 [java] FAIL: apollo/spark/components/Window/skin/window_skin_titleBar_tests titleBar_test2_SparkChrome [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/styles/baselines/skinClass_test1.png.bad.png length: 451 [java] FAIL: apollo/spark/components/Window/styles/window_styles_skinClass1_tests skinClass_test1 [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/styles/baselines/skinClass_test2.png.bad.png length: 1462 [java] FAIL: apollo/spark/components/Window/styles/window_styles_skinClass1_tests skinClass_test2 [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/styles/baselines/skinClass_test3.png.bad.png length: 1410 [java] FAIL: apollo/spark/components/Window/styles/window_styles_skinClass1_tests skinClass_test3 [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/styles/baselines/skinClass_test4.png.bad.png length: 451 [java] FAIL: apollo/spark/components/Window/styles/window_styles_skinClass2_tests skinClass_test4 [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/styles/baselines/skinClass_test5.png.bad.png length: 1462 [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/styles/baselines/skinClass1_test1.png.bad.png length: 451 [java] FAIL: apollo/spark/components/Window/styles/window_styles_skinClass2_tests skinClass_test5 [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/styles/baselines/skinClass1_test2.png.bad.png length: 1462 [java] FAIL: apollo/spark/components/Window/styles/window_styles_skinClass_tests skinClass1_test1 [java] Wrote file: c:/jenkins_slave/workspace/flex-sdk_mustella-air/mustella/tests/apollo/spark/components/Window/styles/baselines/skinClass1_test3.png.bad.png length: 1410 [java] FAIL: apollo/spark/components/Window/styles/window_styles_skinClass_tests skinClass1_test2 [java] FAIL: apollo/spark/components/Window/styles/window_styles_skinClass_tests skinClass1_test3 [java] SCRIPTDONE! 06:26:24.122 [java] GET /ScriptComplete?0 HTTP/1.1
Re: Installer now supports nightly builds!
On 6/29/13 12:39 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: Thanks to Erik's fix for the MD5 checksum comparison issue, we now have support for installing nightly releases from the Apache build server. Excellent! Thanks for doing that. I fixed a couple of bugs and did some cosmetic changes. It looks like the Installer is ready for its next release. How is the Flex SDK release looking? On my Windows machine, Mustella passed (haven't run mobile or AIR though). I'm ready although I think Justin still wants to finish Linux support. -Alex
Jenkins build is back to normal : flex-sdk_asdoc #52
See https://builds.apache.org/job/flex-sdk_asdoc/52/
Build failed in Jenkins: flex-sdk_mustella-mobile #15
See http://localhost:8080/job/flex-sdk_mustella-mobile/15/ -- [...truncated 19097 lines...] [java] clobberProcess true [java] ClobberProcess, destroying process [java] unpacked result: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenu.xml Failed Timed out 0 Sat Jun 29 09:37:27 ACT 2013 0.0 [java] removing the xml app file [java] Grab log, do parse = false [java] Grabbing the log from: C:\Users\ApacheFlex\AppData/Roaming\Macromedia/Flash Player/Logs/flashlog.txt to: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenu.log [java] Grablog: never saw the ScriptDone for C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenu.swf [java] apollo adj with : C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.swf [java] apollo adj thinks it's a swf [java] writing Apollo file! [java] full swf is C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.swf [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.xml [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] getting directory from the swf file [java] derived directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs [java] Launching: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.xml -screensize 640x960:640x960 -profile mobileDevice -XscreenDPI 240 Launching: C:\ApacheFlex\dependencies\AdobeAIRSDK\bin\adl.exe C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.xml [java] USING directory: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs [java] time: 09:37:39.288 [java] Total Results so far: 32 [java] Total Results so far: 32 [java] removing the xml app file [java] Grab log, do parse = false [java] Grabbing the log from: C:\Users\ApacheFlex\AppData/Roaming\Macromedia/Flash Player/Logs/flashlog.txt to: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuCustom.log [java] apollo adj with : C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuScale240.swf [java] apollo adj thinks it's a swf [java] writing Apollo file! [java] full swf is C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuScale240.swf [java] post ApolloAdjuster: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuScale240.xml [java] new test file: C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuScale240.xml [java] cmdArr before: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuScale240.xml [java] moreParameters before: [java] -screensize [java] 640x960:640x960 [java] -profile [java] mobileDevice [java] -XscreenDPI [java] 240 [java] cmdArr after: [java] C:\ApacheFlex\dependencies\AdobeAIRSDK\bin\adl.exe [java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\components\ViewMenu\swfs\ViewMenuScale240.xml [java] -screensize [java] 640x960:640x960
Re: Mustella VM emails to 'issues'?
Ok, I think commits@ is it. Om's argument hits home, builds break because of commits :-) If no major objections, I'll implement this the coming week. EdB On Sat, Jun 29, 2013 at 9:27 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: I think commits@f.a.o would be the best place. Builds break because of bad commits (most of the times) Moreover an additional list (ex. builds@f.a.o) would be a bit of an overkill. Thanks, Om On Sat, Jun 29, 2013 at 12:16 AM, Frédéric THOMAS webdoubl...@hotmail.comwrote: commits@ or issues@ I would say what is better but what is sure is it pollutes the dev list. Those 2 lists are followed as well by committers or at least PMCs, otherwise what do you thing about another list builds@ ? does it worth ? -Fred -Message d'origine- From: Alex Harui Sent: Friday, June 28, 2013 4:35 PM To: dev@flex.apache.org Subject: Re: Mustella VM emails to 'issues'? On 6/28/13 12:32 AM, Erik de Bruin e...@ixsoftware.nl wrote: Hi, I was just wondering: would it be better if I have Jenkins send the Mustella run emails to 'issues@'? Wouldn't commits@ be better? The way it stands now, all three runs (main, AIR and mobile) have tests failing (even after -failures). This means that per full run, three emails will be sent... twice a day. That will put even Justin's JIRA email production to shame ;-) I think it will be cleaner if I direct those emails somewhere they don't interfere with the 'regular' discussions? I'll try to spend some time cleaning up the runs next week. -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Installer now supports nightly builds!
Om, Excellent work, thanks! EdB On Sat, Jun 29, 2013 at 4:10 PM, Alex Harui aha...@adobe.com wrote: On 6/29/13 12:39 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: Thanks to Erik's fix for the MD5 checksum comparison issue, we now have support for installing nightly releases from the Apache build server. Excellent! Thanks for doing that. I fixed a couple of bugs and did some cosmetic changes. It looks like the Installer is ready for its next release. How is the Flex SDK release looking? On my Windows machine, Mustella passed (haven't run mobile or AIR though). I'm ready although I think Justin still wants to finish Linux support. -Alex -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Build failed in Jenkins: flex-sdk_mustella #193
See http://localhost:8080/job/flex-sdk_mustella/193/ -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on WindowsSlave in workspace http://localhost:8080/job/flex-sdk_mustella/ws/ Checkout:flex-sdk_mustella / http://localhost:8080/job/flex-sdk_mustella/ws/ - hudson.remoting.Channel@fa8ba9:WindowsSlave Using strategy: Default Last Built Revision: Revision 588e0aba4df4a6e8825d66cd6124179a9ba540a7 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from origin Commencing build of Revision 588e0aba4df4a6e8825d66cd6124179a9ba540a7 (origin/develop) Checking out Revision 588e0aba4df4a6e8825d66cd6124179a9ba540a7 (origin/develop) FATAL: Could not checkout null with start point 588e0aba4df4a6e8825d66cd6124179a9ba540a7 hudson.plugins.git.GitException: Could not checkout null with start point 588e0aba4df4a6e8825d66cd6124179a9ba540a7 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:878) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1229) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1205) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Thread.java:619) Caused by: hudson.plugins.git.GitException: Command C:\Program Files (x86)\Git\bin\git.exe checkout -f 588e0aba4df4a6e8825d66cd6124179a9ba540a7 returned status code 1: stdout: stderr: error: unable to create file mustella/jenkins.sh (Permission denied) HEAD is now at 588e0ab... Explicitly exit with an error code when there are failures left after running with '-failures'… Without this code the script 'jenkins.sh' will complete successfully - as nothing went wrong with it - and Jenkins won't report on the failures :-( at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:774) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:740) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:750) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkout(CliGitAPIImpl.java:855) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:865) ... 13 more
Re: Mustella VM emails to 'issues'?
On Fri, Jun 28, 2013 at 12:55 AM, Justin Mclean jus...@classsoftware.comwrote: Hi, I was just wondering: would it be better if I have Jenkins send the Mustella run emails to 'issues@'? +0 from me. Someone may break the build and not be aware of it, but if others think that's OK go ahead, I guess someone could politely point it out and suggest they subscribe to issues@ when it occurs. Just to assuage this concern, we have already configured JIRA to send separate emails to the individuals who broke the build, in addition to mailing the list. Thanks, Om
Re: Mustella VM emails to 'issues'?
And just to correct a minor issue with Om's statement: I sure he meant Jenkins, not JIRA :-) EdB On Saturday, June 29, 2013, OmPrakash Muppirala wrote: On Fri, Jun 28, 2013 at 12:55 AM, Justin Mclean jus...@classsoftware.comjavascript:; wrote: Hi, I was just wondering: would it be better if I have Jenkins send the Mustella run emails to 'issues@'? +0 from me. Someone may break the build and not be aware of it, but if others think that's OK go ahead, I guess someone could politely point it out and suggest they subscribe to issues@ when it occurs. Just to assuage this concern, we have already configured JIRA to send separate emails to the individuals who broke the build, in addition to mailing the list. Thanks, Om -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
