RE: [Builds/Jenkins] Help and advise needed
Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down... - the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, he feels entitled to use our builds to experiment. I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly. The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects... Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning. Thanks! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
AW: [Builds/Jenkins] Help and advise needed
Hi, what exactly is the current Problem? As far as I understood, the stability of the build-server seems to be a Problem. I had similar Problems when Setting up the Flexmojos CI Server. After doing all sorts of Amazon EC2, MS Azure VM stuff, I did a fallback to a central CI Server and multiple Agents installed on normal Desktop PCs. So eventually this could be an Option for us. Setting up Jenkins Agents on our own machines, but having the central CI Server, so a build is done as soon as any Agent is available. This way we don't have to rely on the Apache Windows Agent being available. As far as I know another incubating Project (NPanday - .Net Maven Plugin) has to rely on this machine too and they are having Major Problems with it. Mabe private Agents could be a solution. For Flexmojos it certainly helped. Chris Von: Maurice Amsellem maurice.amsel...@systar.com Gesendet: Montag, 9. Dezember 2013 09:16 An: dev@flex.apache.org Betreff: RE: [Builds/Jenkins] Help and advise needed Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down... - the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, he feels entitled to use our builds to experiment. I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly. The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects... Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning. Thanks! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Yes, my thoughts exactly. Two things: we cannot change or even check the settings of the machines themselves, we only have access through the Jenkins web interface. And the most worrying thing: the builds also don't work anymore on the original (windows1) machine. EdB On Mon, Dec 9, 2013 at 9:43 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Hi,
Just checked and here's the config:
AIR_HOME=${WORKSPACE}/air/AIR Integration Kit
FLASHPLAYER_DEBUGGER=C\:/Program\ Files\
(x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
PLAYERGLOBAL_HOME=${WORKSPACE}/lib/player
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\ CS5/Pixel\
Bender\ Toolkit\ 2
This matches the original config:
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\ CS5/Pixel\
Bender\ Toolkit\ 2
So my guess is it hasn't been installed, I'll ask the question on builds@.
Thanks,
Justin
RE: [Builds/Jenkins] Help and advise needed
Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. Thanks, Justin
Re: [Builds/Jenkins] Help and advise needed
I already did... twice.
EdB
On Mon, Dec 9, 2013 at 9:49 AM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
Just checked and here's the config:
AIR_HOME=${WORKSPACE}/air/AIR Integration Kit
FLASHPLAYER_DEBUGGER=C\:/Program\ Files\
(x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
PLAYERGLOBAL_HOME=${WORKSPACE}/lib/player
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
CS5/Pixel\ Bender\ Toolkit\ 2
This matches the original config:
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
CS5/Pixel\ Bender\ Toolkit\ 2
So my guess is it hasn't been installed, I'll ask the question on builds@.
Thanks,
Justin
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. 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
RE: [Builds/Jenkins] Help and advise needed
1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. 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
[DISCUSS] flex-antTasks: HtmlWrapperTask
The current version of the Ant html-wrapper task doesn't supports to use external files. Instead it only uses its embedded template resources - /history - history.css - history.js - historyFrame.html - expressInstall.swf - index.template.html - swfobject.js I added a wrapperFile parameter to the HtmlWrapperTask, so I can use a project specific HTML wrapper file. That's fine for me and is working faultless. The question is now: Would it be more reasonable to parameterize the entire directory (templateDir) instead of only doing it for the HTML template? Or should it be possible to use both - either templateDir or wrapperFile? Thanks, Stephan
Re: [Builds/Jenkins] Help and advise needed
I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. EdB On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: 1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. 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 -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Hi, Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. For development and testing purposes only of course :-) If it's not an officially voted on release then that's all it can be used for. Have a working CI system that run after you check something in IMO is priority no 1 and the nightly build is just a nice little bonus that make life easier for a few folk. It's not actually required as anyone can build the software (with a little bit of effort) from the repo. Thanks, Justin
RE: [Builds/Jenkins] Help and advise needed
I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. I am just going to run some builds, and change some variables. Everything reversible. Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. EdB On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: 1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. 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 -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Exactly. Usually CI is just for checking. But until the Installer can create a working FlexJS SDK, the people wanting to play with it, like the nice folks from FDK, mostly have to rely on the nightly builds. The certainly can build an SDK themselves, but I don't think they need to waste their time having to do that over and over again. If we want to maintain our momentum, this seems very important to me. Living without the flex-sdk builds for a while isn't all that bad in itself, as the Mustella VM catches most of what they do and much more... EdB On Mon, Dec 9, 2013 at 10:30 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. For development and testing purposes only of course :-) If it's not an officially voted on release then that's all it can be used for. Have a working CI system that run after you check something in IMO is priority no 1 and the nightly build is just a nice little bonus that make life easier for a few folk. It's not actually required as anyone can build the software (with a little bit of effort) from the repo. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
I have set up the sample pixelbender job on mustella VM. Now, I need to remove the Interact with desktop option in Jenkins windows service and restart it. Can this be done without risk of the service not restarting properly? Will the slave agent be restarted automatically? Or does it need to be launched manually? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 9 décembre 2013 10:30 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. I am just going to run some builds, and change some variables. Everything reversible. Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. EdB On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: 1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. 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 -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-) EdB On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I have set up the sample pixelbender job on mustella VM. Now, I need to remove the Interact with desktop option in Jenkins windows service and restart it. Can this be done without risk of the service not restarting properly? Will the slave agent be restarted automatically? Or does it need to be launched manually? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 9 décembre 2013 10:30 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. I am just going to run some builds, and change some variables. Everything reversible. Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. EdB On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: 1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. 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 -- 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
RE: [Builds/Jenkins] Help and advise needed
I back back everything (mainly checked Interact with desktop, then restarted the jenkins service and launched WindowsSlave through jnlp. But it now fails to connection to master, ( retries 10 times, then aborts). Note: I did Prepare for shutdown before stopping the service, but apparently , it didn't stop properly. Maybe there are some ports still used or some ghosts processes still running. What should I do now ? restart the VM? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 11:13 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-) EdB On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I have set up the sample pixelbender job on mustella VM. Now, I need to remove the Interact with desktop option in Jenkins windows service and restart it. Can this be done without risk of the service not restarting properly? Will the slave agent be restarted automatically? Or does it need to be launched manually? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 9 décembre 2013 10:30 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. I am just going to run some builds, and change some variables. Everything reversible. Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. EdB On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: 1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location. Thanks, Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T.
RE: [Builds/Jenkins] Help and advise needed
Sounds like a good idea to restart the instance. Then run his start scripts. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Monday, December 09, 2013 5:59 AM To: dev@flex.apache.org Subject: RE: [Builds/Jenkins] Help and advise needed I back back everything (mainly checked Interact with desktop, then restarted the jenkins service and launched WindowsSlave through jnlp. But it now fails to connection to master, ( retries 10 times, then aborts). Note: I did Prepare for shutdown before stopping the service, but apparently , it didn't stop properly. Maybe there are some ports still used or some ghosts processes still running. What should I do now ? restart the VM? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 11:13 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-) EdB On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I have set up the sample pixelbender job on mustella VM. Now, I need to remove the Interact with desktop option in Jenkins windows service and restart it. Can this be done without risk of the service not restarting properly? Will the slave agent be restarted automatically? Or does it need to be launched manually? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 9 décembre 2013 10:30 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. I am just going to run some builds, and change some variables. Everything reversible. Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. EdB On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: 1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Hi, I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be
RE: [Builds/Jenkins] Help and advise needed
A session log-off was apparently enough. Ouf ! Maurice -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : lundi 9 décembre 2013 12:08 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed Sounds like a good idea to restart the instance. Then run his start scripts. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Monday, December 09, 2013 5:59 AM To: dev@flex.apache.org Subject: RE: [Builds/Jenkins] Help and advise needed I back back everything (mainly checked Interact with desktop, then restarted the jenkins service and launched WindowsSlave through jnlp. But it now fails to connection to master, ( retries 10 times, then aborts). Note: I did Prepare for shutdown before stopping the service, but apparently , it didn't stop properly. Maybe there are some ports still used or some ghosts processes still running. What should I do now ? restart the VM? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 11:13 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-) EdB On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I have set up the sample pixelbender job on mustella VM. Now, I need to remove the Interact with desktop option in Jenkins windows service and restart it. Can this be done without risk of the service not restarting properly? Will the slave agent be restarted automatically? Or does it need to be launched manually? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 9 décembre 2013 10:30 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. I am just going to run some builds, and change some variables. Everything reversible. Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. EdB On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: 1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties. So there is a possibility that they were not set the same in the new machine. Makes sense ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : lundi 9 décembre 2013 09:43 À :
RE: git commit: [flex-sdk] [refs/heads/develop] - FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed.
It's an interesting concept, but since we do not have a solid open-source skin drawing application, we need a different solution. Styles make sense in that the skin has the same components but can be adjusted with styles/CSS. Which should also work with the new FlexJS. It's probably better it doesn't affect custom skins... if they customized them, they had a specific design in mind and probably wouldn't want it changing by itself. I added the default placement (in defaults.css) to be to the right which is what the current skin sets up. If we want we can also add the case statement to default any non-matching string values to the right as well. s:Label id=labelDisplay textAlign=start verticalAlign=middle maxDisplayedLines=1 left=18 right=0 top=3 bottom=3 verticalCenter=2 / -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, December 09, 2013 12:19 AM To: dev@flex.apache.org; comm...@flex.apache.org Subject: Re: git commit: [flex-sdk] [refs/heads/develop] - FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed. FWIW, at one point in time, Spark skins were supposed to have as few styles as possible since tools like Catalyst were supposed to make easier to just draw a different skin and not have to implement as much code in the skin. Custom skins were supposed to simply place the icon wherever it should be in relation to the label. Existing custom skins/themes certainly will not respond to this new option. That said, I'm not saying you should revert. I'm just pointing this out to see if anyone else cares. I think some Spark skins respond to custom non-font styles already. One other thing: should the case statement handle the default case as LEFT? If someone has a custom CSS file but use the default skin, they won't pick up this new style then will the skin still work as it used to? On 12/8/13 1:01 PM, mkess...@apache.org mkess...@apache.org wrote: Updated Branches: refs/heads/develop 7c3d70818 - cdcb49242 FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed. Project: http://git-wip-us.apache.org/repos/asf/flex-sdk/repo Commit: http://git-wip-us.apache.org/repos/asf/flex-sdk/commit/cdcb4924 Tree: http://git-wip-us.apache.org/repos/asf/flex-sdk/tree/cdcb4924 Diff: http://git-wip-us.apache.org/repos/asf/flex-sdk/diff/cdcb4924 Branch: refs/heads/develop Commit: cdcb49242ae0d06645d3ebaf4f7e3c102b8f6506 Parents: 7c3d708 Author: Mark Kessler kesslerconsult...@gmail.com Authored: Sun Dec 8 15:59:25 2013 -0500 Committer: Mark Kessler kesslerconsult...@gmail.com Committed: Sun Dec 8 15:59:25 2013 -0500 -- .../spark/src/spark/components/CheckBox.as | 188 --- .../src/spark/skins/spark/CheckBoxSkin.mxml | 138 ++ 2 files changed, 138 insertions(+), 188 deletions(-) -- http://git-wip-us.apache.org/repos/asf/flex-sdk/blob/cdcb4924/frameworks/p rojects/spark/src/spark/components/CheckBox.as -- diff --git a/frameworks/projects/spark/src/spark/components/CheckBox.as b/frameworks/projects/spark/src/spark/components/CheckBox.as index 77dd23d..c72f6c8 100644 --- a/frameworks/projects/spark/src/spark/components/CheckBox.as +++ b/frameworks/projects/spark/src/spark/components/CheckBox.as @@ -24,9 +24,7 @@ import flash.events.Event; import flash.events.MouseEvent; import mx.core.mx_internal; -import mx.core.UIComponent; -import spark.components.supportClasses.LabelPlacement; import spark.components.supportClasses.ToggleButtonBase; use namespace mx_internal; @@ -214,30 +212,6 @@ public class CheckBox extends ToggleButtonBase // -- // -// Variables -// - // -- - -//-- -// checkDisplay -//-- - -/** - * The skin part that defines the CheckBox grouping. - * - * @see spark.skins.spark.CheckBoxSkin#checkDisplay - * - * @langversion 3.0 - * @playerversion Flash 11.8 - * @playerversion AIR 3.8 - * @productversion Flex 4.12 - */ -[SkinPart(required=false)] -public var checkDisplay:UIComponent; - - - // -- -// // Properties // // -- @@ -323,120 +297,6 @@ public class CheckBox extends ToggleButtonBase // -- // -// Methods -
RE: flex-sdk_mustella - Build # 603 - Still Failing!
Index file locked? Says to remove the file manually. -Mark -Original Message- From: flex.muste...@gmail.com [mailto:flex.muste...@gmail.com] Sent: Monday, December 09, 2013 6:10 AM To: comm...@flex.apache.org; jmcl...@apache.org; kesslerconsult...@gmail.com; maurice.amsel...@systar.com Subject: flex-sdk_mustella - Build # 603 - Still Failing! flex-sdk_mustella - Build # 603 - Still Failing: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/603/ Changes for Build #600 [KesslerConsulting] FLEX-33984: Added support for labelPlacement on s:CheckBox. [KesslerConsulting] FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed. [KesslerConsulting] FLEX-33984: Corrected an ASDOC comment. [maurice.amsellem] FIX FLEX-33860 IOS7 Changes for Build #601 Changes for Build #602 Changes for Build #603 Started by timer [EnvInject] - Loading node environment variables. Building remotely on WindowsSlave in workspace c:\jenkins_slave\workspace\flex-sdk_mustella Checkout:flex-sdk_mustella / c:\jenkins_slave\workspace\flex-sdk_mustella - hudson.remoting.Channel@672bb3:WindowsSlave Using strategy: Default Last Built Revision: Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from origin Commencing build of Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Checking out Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) FATAL: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 hudson.plugins.git.GitException: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 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 27be89a0537d1e47cbe923be578ed9f318449b04 returned status code 128: stdout: stderr: fatal: Unable to create 'c:/jenkins_slave/workspace/flex-sdk_mustella/.git/index.lock': File exists. If no other git process is currently running, this probably means a git process crashed in this repository earlier. Make sure no other git process is running and remove the file manually to continue. 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 (sent from ext-email) smime.p7s Description: S/MIME cryptographic signature
RE: flex-sdk_mustella - Build # 603 - Still Failing!
I had to cancel some jobs manually to make som tests on the mustella VM and it's showing these errors when restarting. Nothing to worry about. Now the builds are operational again. Still have to wait until the next run. Maurice -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : lundi 9 décembre 2013 13:21 À : dev@flex.apache.org Objet : RE: flex-sdk_mustella - Build # 603 - Still Failing! Index file locked? Says to remove the file manually. -Mark -Original Message- From: flex.muste...@gmail.com [mailto:flex.muste...@gmail.com] Sent: Monday, December 09, 2013 6:10 AM To: comm...@flex.apache.org; jmcl...@apache.org; kesslerconsult...@gmail.com; maurice.amsel...@systar.com Subject: flex-sdk_mustella - Build # 603 - Still Failing! flex-sdk_mustella - Build # 603 - Still Failing: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/603/ Changes for Build #600 [KesslerConsulting] FLEX-33984: Added support for labelPlacement on s:CheckBox. [KesslerConsulting] FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed. [KesslerConsulting] FLEX-33984: Corrected an ASDOC comment. [maurice.amsellem] FIX FLEX-33860 IOS7 Changes for Build #601 Changes for Build #602 Changes for Build #603 Started by timer [EnvInject] - Loading node environment variables. Building remotely on WindowsSlave in workspace c:\jenkins_slave\workspace\flex-sdk_mustella Checkout:flex-sdk_mustella / c:\jenkins_slave\workspace\flex-sdk_mustella - hudson.remoting.Channel@672bb3:WindowsSlave Using strategy: Default Last Built Revision: Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from origin Commencing build of Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Checking out Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) FATAL: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 hudson.plugins.git.GitException: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 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 27be89a0537d1e47cbe923be578ed9f318449b04 returned status code 128: stdout: stderr: fatal: Unable to create 'c:/jenkins_slave/workspace/flex-sdk_mustella/.git/index.lock': File exists. If no other git process is currently running, this probably means a git process crashed in this repository earlier. Make sure no other git process is running and remove the file manually to continue. 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 (sent from ext-email)
RE: [Builds/Jenkins] Help and advise needed
BTW, the test with unchecking Interact with desktop didn't give any result (didn't fail). -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 9 décembre 2013 12:12 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed A session log-off was apparently enough. Ouf ! Maurice -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : lundi 9 décembre 2013 12:08 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed Sounds like a good idea to restart the instance. Then run his start scripts. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Monday, December 09, 2013 5:59 AM To: dev@flex.apache.org Subject: RE: [Builds/Jenkins] Help and advise needed I back back everything (mainly checked Interact with desktop, then restarted the jenkins service and launched WindowsSlave through jnlp. But it now fails to connection to master, ( retries 10 times, then aborts). Note: I did Prepare for shutdown before stopping the service, but apparently , it didn't stop properly. Maybe there are some ports still used or some ghosts processes still running. What should I do now ? restart the VM? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 11:13 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-) EdB On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: I have set up the sample pixelbender job on mustella VM. Now, I need to remove the Interact with desktop option in Jenkins windows service and restart it. Can this be done without risk of the service not restarting properly? Will the slave agent be restarted automatically? Or does it need to be launched manually? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : lundi 9 décembre 2013 10:30 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. I am just going to run some builds, and change some variables. Everything reversible. Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place. Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest. EdB On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: 1) On this thread: https://twitter.com/bigosmallm/status/308466759130816512 Kevin answering to Om says: [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work. So could it be something like Jenkins service permissions ? Is the service running as Local system, and Interact with desktop checked ? or is it running on a dedicated account? 2) what about experimenting on our mustella vm? We could install pixel bender, and try the pixel bender compile with different settings, see if we can reproduce the AIF error. Of course, that would temporarily break the mustella tests... Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:01 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config. EdB On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Ok, never mind. So what else could it be? Does someone know how to reproduce the AIF Internal exception in pixel-bender compiler ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 09:52 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine. EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Hi, I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env
RE: flex-sdk_mustella - Build # 603 - Still Failing!
Thanks Maurice. -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Monday, December 09, 2013 7:37 AM To: dev@flex.apache.org Subject: RE: flex-sdk_mustella - Build # 603 - Still Failing! I had to cancel some jobs manually to make som tests on the mustella VM and it's showing these errors when restarting. Nothing to worry about. Now the builds are operational again. Still have to wait until the next run. Maurice -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : lundi 9 décembre 2013 13:21 À : dev@flex.apache.org Objet : RE: flex-sdk_mustella - Build # 603 - Still Failing! Index file locked? Says to remove the file manually. -Mark -Original Message- From: flex.muste...@gmail.com [mailto:flex.muste...@gmail.com] Sent: Monday, December 09, 2013 6:10 AM To: comm...@flex.apache.org; jmcl...@apache.org; kesslerconsult...@gmail.com; maurice.amsel...@systar.com Subject: flex-sdk_mustella - Build # 603 - Still Failing! flex-sdk_mustella - Build # 603 - Still Failing: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/603/ Changes for Build #600 [KesslerConsulting] FLEX-33984: Added support for labelPlacement on s:CheckBox. [KesslerConsulting] FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed. [KesslerConsulting] FLEX-33984: Corrected an ASDOC comment. [maurice.amsellem] FIX FLEX-33860 IOS7 Changes for Build #601 Changes for Build #602 Changes for Build #603 Started by timer [EnvInject] - Loading node environment variables. Building remotely on WindowsSlave in workspace c:\jenkins_slave\workspace\flex-sdk_mustella Checkout:flex-sdk_mustella / c:\jenkins_slave\workspace\flex-sdk_mustella - hudson.remoting.Channel@672bb3:WindowsSlave Using strategy: Default Last Built Revision: Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from origin Commencing build of Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Checking out Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) FATAL: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 hudson.plugins.git.GitException: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 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 27be89a0537d1e47cbe923be578ed9f318449b04 returned status code 128: stdout: stderr: fatal: Unable to create 'c:/jenkins_slave/workspace/flex-sdk_mustella/.git/index.lock': File exists. If no other git process is currently running, this probably means a git process crashed in this repository earlier. Make sure no other git process is running and remove the file manually to continue. 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 (sent from ext-email) smime.p7s Description: S/MIME cryptographic signature
Re: flex-sdk_mustella - Build # 603 - Still Failing!
That happens from time to time (as Maurice said, mostly while messing with the builds). In my experience only a manual removal of that file and a reboot of the machine solves this... but we'll see. EdB On Mon, Dec 9, 2013 at 1:20 PM, Kessler CTR Mark J mark.kessler@usmc.mil wrote: Index file locked? Says to remove the file manually. -Mark -Original Message- From: flex.muste...@gmail.com [mailto:flex.muste...@gmail.com] Sent: Monday, December 09, 2013 6:10 AM To: comm...@flex.apache.org; jmcl...@apache.org; kesslerconsult...@gmail.com; maurice.amsel...@systar.com Subject: flex-sdk_mustella - Build # 603 - Still Failing! flex-sdk_mustella - Build # 603 - Still Failing: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/603/ Changes for Build #600 [KesslerConsulting] FLEX-33984: Added support for labelPlacement on s:CheckBox. [KesslerConsulting] FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed. [KesslerConsulting] FLEX-33984: Corrected an ASDOC comment. [maurice.amsellem] FIX FLEX-33860 IOS7 Changes for Build #601 Changes for Build #602 Changes for Build #603 Started by timer [EnvInject] - Loading node environment variables. Building remotely on WindowsSlave in workspace c:\jenkins_slave\workspace\flex-sdk_mustella Checkout:flex-sdk_mustella / c:\jenkins_slave\workspace\flex-sdk_mustella - hudson.remoting.Channel@672bb3:WindowsSlave Using strategy: Default Last Built Revision: Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from origin Commencing build of Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Checking out Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) FATAL: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 hudson.plugins.git.GitException: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 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 27be89a0537d1e47cbe923be578ed9f318449b04 returned status code 128: stdout: stderr: fatal: Unable to create 'c:/jenkins_slave/workspace/flex-sdk_mustella/.git/index.lock': File exists. If no other git process is currently running, this probably means a git process crashed in this repository earlier. Make sure no other git process is running and remove the file manually to continue. 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 (sent from ext-email) -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: flex-sdk_mustella - Build # 603 - Still Failing!
Didn't work. I had to manually delete index.lock like you said. -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 13:59 À : dev@flex.apache.org Objet : Re: flex-sdk_mustella - Build # 603 - Still Failing! That happens from time to time (as Maurice said, mostly while messing with the builds). In my experience only a manual removal of that file and a reboot of the machine solves this... but we'll see. EdB On Mon, Dec 9, 2013 at 1:20 PM, Kessler CTR Mark J mark.kessler@usmc.mil wrote: Index file locked? Says to remove the file manually. -Mark -Original Message- From: flex.muste...@gmail.com [mailto:flex.muste...@gmail.com] Sent: Monday, December 09, 2013 6:10 AM To: comm...@flex.apache.org; jmcl...@apache.org; kesslerconsult...@gmail.com; maurice.amsel...@systar.com Subject: flex-sdk_mustella - Build # 603 - Still Failing! flex-sdk_mustella - Build # 603 - Still Failing: http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/603/ Changes for Build #600 [KesslerConsulting] FLEX-33984: Added support for labelPlacement on s:CheckBox. [KesslerConsulting] FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed. [KesslerConsulting] FLEX-33984: Corrected an ASDOC comment. [maurice.amsellem] FIX FLEX-33860 IOS7 Changes for Build #601 Changes for Build #602 Changes for Build #603 Started by timer [EnvInject] - Loading node environment variables. Building remotely on WindowsSlave in workspace c:\jenkins_slave\workspace\flex-sdk_mustella Checkout:flex-sdk_mustella / c:\jenkins_slave\workspace\flex-sdk_mustella - hudson.remoting.Channel@672bb3:WindowsSlave Using strategy: Default Last Built Revision: Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Fetching changes from 1 remote Git repository Fetching upstream changes from origin Commencing build of Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) Checking out Revision 27be89a0537d1e47cbe923be578ed9f318449b04 (origin/develop) FATAL: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 hudson.plugins.git.GitException: Could not checkout null with start point 27be89a0537d1e47cbe923be578ed9f318449b04 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 27be89a0537d1e47cbe923be578ed9f318449b04 returned status code 128: stdout: stderr: fatal: Unable to create 'c:/jenkins_slave/workspace/flex-sdk_mustella/.git/index.lock': File exists. If no other git process is currently running, this probably means a git process crashed in this repository earlier. Make sure no other git process is running and remove the file manually to continue. 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 (sent from ext-email) -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [DISCUSS] flex-antTasks: HtmlWrapperTask
Personally, I've always used ant to automate the wrappers. Just my 2 cents. On Dec 9, 2013 4:17 AM, Stephan Plath flex-...@gmx.net wrote: The current version of the Ant html-wrapper task doesn't supports to use external files. Instead it only uses its embedded template resources - /history - history.css - history.js - historyFrame.html - expressInstall.swf - index.template.html - swfobject.js I added a wrapperFile parameter to the HtmlWrapperTask, so I can use a project specific HTML wrapper file. That's fine for me and is working faultless. The question is now: Would it be more reasonable to parameterize the entire directory (templateDir) instead of only doing it for the HTML template? Or should it be possible to use both - either templateDir or wrapperFile? Thanks, Stephan
Re: [DISCUSS] flex-antTasks: HtmlWrapperTask
While you're in ant, automate your project assets also. Setup a main workspace asset repo, pull files from there. Another good trick, if you have multiple projects that work together, use ant to create a main output folder and compile files there. On Dec 9, 2013 4:17 AM, Stephan Plath flex-...@gmx.net wrote: The current version of the Ant html-wrapper task doesn't supports to use external files. Instead it only uses its embedded template resources - /history - history.css - history.js - historyFrame.html - expressInstall.swf - index.template.html - swfobject.js I added a wrapperFile parameter to the HtmlWrapperTask, so I can use a project specific HTML wrapper file. That's fine for me and is working faultless. The question is now: Would it be more reasonable to parameterize the entire directory (templateDir) instead of only doing it for the HTML template? Or should it be possible to use both - either templateDir or wrapperFile? Thanks, Stephan
Re: AS3 on the server
The Uriana J2EE and J2EE GWT ports are downloadable from
https://www.assembla.com/code/uriana/subversion/nodes/128/trunk the Uriana
repository.
I am currently working to embed GWT remote Objects architecture within the
framework architecture, which I hope that will take no much longer to be
accomplished.
I am also preparing some powerpoint documentation to get ready to work with
Uriana for GWT projects.
Cheers.
2013/12/2 Alain Ekambi jazzmatad...@gmail.com
@Carlos
That sounds cool.
Any link ?
2013/12/2 Carlos Velasco carlos.velasco.bla...@gmail.com
Talking on GWT, I've recently ported Uriana to suit with GWT projects and
we're currently testing it at several enterprise projects. The code is at
Uriana's SVN site.
2013/12/2 Alain Ekambi jazzmatad...@gmail.com
Another reason why you guyz should switch to GWT :)
Java all the way to the backend :)
2013/12/2 Mr. Rich mrrich@gmail.com
Here's a solution. Because Adobe didn't release this for AS3, I
built
it
into FTML a few years back!
1. RSL support - FMTL will load any swf as an RSL and allow you call
any
method or construct any class using your swf file.
2. MXML web compiler - FTML will allow you compile mxml code directly
on
the HTML page - and it works as you would expect, similar to Flash
Builder
where you only need to define the namespace of the class.
Most of what I just said can be found here:
http://reshapemedia.com/ftml/learn/runtime-libraries/
3. Web based AS3 - FTML has multiple scripting support where you can
(1)
write code in javascript and pass data between js and flash, (2)
write
pure
AS3 code (like Java so flash.display.DisplayOjbect not DisplayObject)
4. All flash code is IN THE BROWSER, NO COMPILING - only refresh and
go!
5. PHP and flash - FTML is a markup so you can use it just like HTML
with
PHP no extra config required:
http://reshapemedia.com/ftml/learn/php-to-flash/
6. Javascript and flash - fastest integration possible:
http://reshapemedia.com/ftml/learn/javascript-to-flash/
Remember FTML is free - so try it with your swf and see for your
self.
Support is there for 4.6, 4.11 support will come in 2013.
Any questions or comments - mrr...@reshapemedia.com (fastest way to
get
in
touch).
On Mon, Dec 2, 2013 at 10:21 AM, David Coleman
david_coleman_...@hotmail.com wrote:
For what it's worth, I've often shared the opinion that AS3 would
be
an
ideal server language. Strongly structured, native events which in
my
opinion is a world better than java. In my mind the language
itself
is
mature, and elegant and the only thing missing is a strong set of
database
access libs to work as a web service.
as far as how you would implement it as a platform, I always
pictured
that
the ideal situation would be a worker based solution, using workers
for
db
access and a mxml approach for html files, similar to how php can
script
a
page, with the mxml components implemented similar to how CakePHP
implements an element. we can use a flag like ?mx . ?
ie:
index.mhtm:
html
?mx
this.addHere(
HeadElementFactory.getHeadFor(this)
);
?
...
/html
sure this is a fast ugly incomplete example, but what i have
defined
more
clear in my head is how we would do the server
inside an mhtm file we can directly call a server component like:
(Server.getService(FacebookService) as
IFacebookService).getFriends(onFriendsResult);
we would then be able to pass the data to an mhtm element and using
jQuery-ish selectors inject the data into the dom of the parent
page,
or
better yet invent some kind of anchor class that we can use in
the
result
handler to build html directly on the server, inserting content at
a
given
tagged point of the dom. and build out the dom prior to serving the
page
to
the browser.
In terms of mapping a REST (for instance) call,
Server.mapService('{locale}/{controller}/{method}/[named]/{argv}')
again, much, much definition is lacking... but i've given this
great
thought over the years.
I have long thought that AS3 as a language has a UNIQUE advantage
over
other server languages. The SWF encapsulation is a tricky
technical
challenge, and the creation of a stable and robust web service
framework
would obviously be a big task.
but I just thought that maybe, just maybe, it's worth just throwing
this
out there for anyone who might have similar ideas to build on!
So anyway, hope you all like my fantasy server idea... maybe i'm
full
of
it... maybe i'm actually on to something. but I've
Re: [DISCUSS] flex-antTasks: HtmlWrapperTask
Am 09.12.2013 15:32, schrieb Mr. Rich:
Personally, I've always used ant to automate the wrappers.
The Flex SDK is released together with
${FLEX_HOME}/ant/lib/flexTasks.jar which provides the following ant tasks
mxmlc=flex.ant.MxmlcTask
compc=flex.ant.CompcTask
html-wrapper=flex.ant.HtmlWrapperTask
asdoc=flex.ant.AsDocTask
I want to contribute to the HtmlWrapperTask.java with one or two
properties which enable the definition of external templates instead of
using the embedded files. This is merely a tiny enhancement and most
likely or minor interest, but accordingly to the committers wiki section
and my understanding of it, new features should be discussed before
committing.
So the questions is just, what others would prefer how the external
template files should be parameterized or should I just commit the
changes so they fit my own needs?
Thanks, Stephan
Re: [DISCUSS] flex-antTasks: HtmlWrapperTask
IMO, you are welcome to do more, but as long as you don't break existing
functionality, or make it harder to make improvements later, doing just
what you need is completely acceptable, so I think your current set of
proposed changes is fine.
-Alex
On 12/9/13 8:02 AM, Stephan Plath flex-...@gmx.net wrote:
Am 09.12.2013 15:32, schrieb Mr. Rich:
Personally, I've always used ant to automate the wrappers.
The Flex SDK is released together with
${FLEX_HOME}/ant/lib/flexTasks.jar which provides the following ant tasks
mxmlc=flex.ant.MxmlcTask
compc=flex.ant.CompcTask
html-wrapper=flex.ant.HtmlWrapperTask
asdoc=flex.ant.AsDocTask
I want to contribute to the HtmlWrapperTask.java with one or two
properties which enable the definition of external templates instead of
using the embedded files. This is merely a tiny enhancement and most
likely or minor interest, but accordingly to the committers wiki section
and my understanding of it, new features should be discussed before
committing.
So the questions is just, what others would prefer how the external
template files should be parameterized or should I just commit the
changes so they fit my own needs?
Thanks, Stephan
Re: git commit: [flex-sdk] [refs/heads/develop] - FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed.
On 12/9/13 4:01 AM, Kessler CTR Mark J mark.kessler@usmc.mil wrote: It's an interesting concept, but since we do not have a solid open-source skin drawing application, we need a different solution. Styles make sense in that the skin has the same components but can be adjusted with styles/CSS. Which should also work with the new FlexJS. It's probably better it doesn't affect custom skins... if they customized them, they had a specific design in mind and probably wouldn't want it changing by itself. FlexJS skinning is different from Spark/MX skinning. But that's for a different discussion. I added the default placement (in defaults.css) to be to the right which is what the current skin sets up. If we want we can also add the case statement to default any non-matching string values to the right as well. s:Label id=labelDisplay textAlign=start verticalAlign=middle maxDisplayedLines=1 left=18 right=0 top=3 bottom=3 verticalCenter=2 / Sorry, I mixed up left vs. right, but my point is that not everyone uses the defaults.css in the framework but may use the default skin so the skin should do what it used to do if that style is not in the css.
RE: git commit: [flex-sdk] [refs/heads/develop] - FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed.
Ahh that makes sense, I will add the default to automatically set right when I get home. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, December 09, 2013 12:38 PM To: dev@flex.apache.org Subject: Re: git commit: [flex-sdk] [refs/heads/develop] - FLEX-33984: Moved the placement logic from the hostComponent to the skin. Removed some code no longer needed. Sorry, I mixed up left vs. right, but my point is that not everyone uses the defaults.css in the framework but may use the default skin so the skin should do what it used to do if that style is not in the css.
New Flex MaskedTextInput Spark Component
Hi, These days I worked a new spark MaskedTextInput component and I want to share a demo of this component so you can play with it. I think there's no such component already in the Flex SDK or out there, and as I needed for a project I had to make one from scratch. The component is an extension of spark TextInput. I plan to commit this component to Apache Flex SDK in the next days unless someone let me know another alternative or some info that make this component useless. In order to prepare the commit I want to ask other committers and PMCs here where is the appropriate place to hold this component and share what you consider to take into account in order to make a right integration. If someone thinks it's not worth it to make it part of the Flex SDK, let me know as well. I don't want to commit code that could not be right for the SDK. Here's the link to the demo. I posted as well some doc comment text to share the properties you can use: http://www.carlosrovira.com/blog/spark-maskedtextinput-demo/ Hope you consider it interesting and if you know some other similar component out there, please let me know! :) Best, -- -- Carlos Rovira
Re: New Flex MaskedTextInput Spark Component
This is supremely useful, thank you! EdB On Mon, Dec 9, 2013 at 7:28 PM, Carlos Rovira carlosrov...@apache.org wrote: Hi, These days I worked a new spark MaskedTextInput component and I want to share a demo of this component so you can play with it. I think there's no such component already in the Flex SDK or out there, and as I needed for a project I had to make one from scratch. The component is an extension of spark TextInput. I plan to commit this component to Apache Flex SDK in the next days unless someone let me know another alternative or some info that make this component useless. In order to prepare the commit I want to ask other committers and PMCs here where is the appropriate place to hold this component and share what you consider to take into account in order to make a right integration. If someone thinks it's not worth it to make it part of the Flex SDK, let me know as well. I don't want to commit code that could not be right for the SDK. Here's the link to the demo. I posted as well some doc comment text to share the properties you can use: http://www.carlosrovira.com/blog/spark-maskedtextinput-demo/ Hope you consider it interesting and if you know some other similar component out there, please let me know! :) Best, -- -- Carlos Rovira -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down... - the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, he feels entitled to use our builds to experiment. I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly. The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects... Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning. Thanks! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: New Flex MaskedTextInput Spark Component
Awesome stuff Carlos. Does it work with Mobile too? (ie: with StageText) On 09/12/2013 18:28, Carlos Rovira wrote: Hi, These days I worked a new spark MaskedTextInput component and I want to share a demo of this component so you can play with it. I think there's no such component already in the Flex SDK or out there, and as I needed for a project I had to make one from scratch. The component is an extension of spark TextInput. I plan to commit this component to Apache Flex SDK in the next days unless someone let me know another alternative or some info that make this component useless. In order to prepare the commit I want to ask other committers and PMCs here where is the appropriate place to hold this component and share what you consider to take into account in order to make a right integration. If someone thinks it's not worth it to make it part of the Flex SDK, let me know as well. I don't want to commit code that could not be right for the SDK. Here's the link to the demo. I posted as well some doc comment text to share the properties you can use: http://www.carlosrovira.com/blog/spark-maskedtextinput-demo/ Hope you consider it interesting and if you know some other similar component out there, please let me know! :) Best, -- Lee Burrows ActionScripter
Re: [Builds/Jenkins] Help and advise needed
On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down... - the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, he feels entitled to use our builds to experiment. I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly. The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects... Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning. Thanks! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down... - the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, he feels entitled to use our builds to experiment. I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly. The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects... Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning. Thanks! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: New Flex MaskedTextInput Spark Component
Very nice! One thing: The IBAN and Phone masks do not work the way I'd expect. It should jump straight to the numbers. On Dec 9, 2013, at 8:28 PM, Carlos Rovira wrote: Hi, These days I worked a new spark MaskedTextInput component and I want to share a demo of this component so you can play with it. I think there's no such component already in the Flex SDK or out there, and as I needed for a project I had to make one from scratch. The component is an extension of spark TextInput. I plan to commit this component to Apache Flex SDK in the next days unless someone let me know another alternative or some info that make this component useless. In order to prepare the commit I want to ask other committers and PMCs here where is the appropriate place to hold this component and share what you consider to take into account in order to make a right integration. If someone thinks it's not worth it to make it part of the Flex SDK, let me know as well. I don't want to commit code that could not be right for the SDK. Here's the link to the demo. I posted as well some doc comment text to share the properties you can use: http://www.carlosrovira.com/blog/spark-maskedtextinput-demo/ Hope you consider it interesting and if you know some other similar component out there, please let me know! :) Best, -- -- Carlos Rovira
Re: [Builds/Jenkins] Help and advise needed
On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down... - the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, he feels entitled to use our builds to experiment. I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly. The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects... Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning. Thanks! EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: New Flex MaskedTextInput Spark Component
Hey Carlos,
That's great. I'd written a very similar component a few years ago, which
worked pretty much the same as yours except the code was never
publication-worthy ;)
From what I've seen, there are 2 minor differences:
- there was a list of possible separators (which could also be
configured); yours seems to have only one separator. I absolutely needed
this because I created the component initially for a Belgian national
register number which has a mask like this: ##.##.## - ###.## so both the
dots and the dashes had to be separators. This would fix your 'sample phone
mask' and 'sample IBAN mask' which are behaving a bit oddly as Harbs
already mentioned. This is the list of default separators I
used: /\|:-.()[]{} For the 'sample IBAN mask' the developer could then
set separators=ES- to override these defaults.
- you could provide a custom mask like 'dd/mm/' for a date. I'm not
sure, but it looks like your version supports only one mask character at a
time.
I also used this component to create a custom date input which combined the
masked text input and the old mx date picker for better UX than mx
DateField provides.
I don't mind sharing my code, but as I already mentioned, it's a bit dirty
:-/
cheers,
Max
On Mon, Dec 9, 2013 at 8:27 PM, Harbs harbs.li...@gmail.com wrote:
Very nice!
One thing:
The IBAN and Phone masks do not work the way I'd expect. It should jump
straight to the numbers.
On Dec 9, 2013, at 8:28 PM, Carlos Rovira wrote:
Hi,
These days I worked a new spark MaskedTextInput component and I want to
share a demo of this component so you can play with it.
I think there's no such component already in the Flex SDK or out there,
and
as I needed for a project I had to make one from scratch.
The component is an extension of spark TextInput.
I plan to commit this component to Apache Flex SDK in the next days
unless
someone let me know another alternative or some info
that make this component useless. In order to prepare the commit I want
to
ask other committers and PMCs here where is the appropriate place
to hold this component and share what you consider to take into account
in
order to make a right integration. If someone thinks it's not worth it to
make it part of the Flex SDK, let me know as well. I don't want to commit
code that could not be right for the SDK.
Here's the link to the demo. I posted as well some doc comment text to
share the properties you can use:
http://www.carlosrovira.com/blog/spark-maskedtextinput-demo/
Hope you consider it interesting and if you know some other similar
component out there, please let me know! :)
Best,
--
--
Carlos Rovira
Re: New Flex MaskedTextInput Spark Component
Hi, - there was a list of possible separators The mx:DateFormatter validator does this (see parseDateString), you might want to take a look at how it does it. Also you might want to consider how to mask for currency ($ + , + .) and non english dates with multiple separators (eg Japanese date are usually written 2008年12月31日). Also perhaps a nice addition would be able to use a RegEx for masking as you type? Or provide a hook for custom checking like the extraValidation property of the PostCodeValidator. Thanks, Justin
Re: New Flex MaskedTextInput Spark Component
Hi, @Erik, @Maurice, thanks for your kindly words :), this encourages me to commit the component :) @Lee, I must confess that my development is focused on browser so I didn't take StageText into account, but as this is a spark TextInput extension, I think it should work, since it mainly uses two listeners to play with TextEvent and TextOperationEvent. Hope you could help me to test in a mobile device and see if we need to tweak something to make it work or if it works with the actual approach. @Harbs: You're right, as this is a first draft, it only support one separator, so we need to update to more than one to make it work as you expect. It's the next on the list, but I think I'll commit first the actual version and then we can update it to get this feature. @Maxime, very helpful comments, it throws many ideas and experience. If you want to share your code it would be good, but your experience with this stuff is already valuable to update this component. I'll take your recommendations into account to make further enhancements as the one commented before for multiple separators or the kind of multiple placeholders you suggest. As you did, I already has a r:DateField (r is the namespace in my framework Riality) that is basically a mx:DateField with a spark TextInput and a mask logic similar to this component. I'd like to get a spark DateField some day, but I think the focus on spark DateField is more based on flash globalization capabilities than this usability enhancements. But it would be a great addition to the actual unique mx:DateField option to start a s:Datefield official component that use a TextInput component like this ;) @Justin, I'll check your comments to see how we can take into account all this things, but I'm afraid that this initial component is not as smart..maybe with the time and your help we can build such versatile maskedtextinput component. So taking into account that the component is wanted, could you guys point me to the place where I could make a first commit? it will consist of the AS3 class, the basic skin and some CSS styles. Thanks again for your feedback and hope that we could enhance this component to make it better with the comments shared in this thread. Best Carlos 2013/12/9 Justin Mclean jus...@classsoftware.com Hi, - there was a list of possible separators The mx:DateFormatter validator does this (see parseDateString), you might want to take a look at how it does it. Also you might want to consider how to mask for currency ($ + , + .) and non english dates with multiple separators (eg Japanese date are usually written 2008年12月31日). Also perhaps a nice addition would be able to use a RegEx for masking as you type? Or provide a hook for custom checking like the extraValidation property of the PostCodeValidator. Thanks, Justin -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
Re: New Flex MaskedTextInput Spark Component
Hi, @Justin, I'll check your comments to see how we can take into account all this things, but I'm afraid that this initial component is not as smart..maybe with the time and your help we can build such versatile maskedtextinput component. Sure can help out there and tat certainly doesn't need to be done right away. Have a single separator is still useful for a lot of cases. So taking into account that the component is wanted, could you guys point me to the place where I could make a first commit? Two main choices: 1. in frameworks/projects/experimental 2. in frameworks/projects/apache I'd go with 1. if you think it still needs a bit of work or is missing tests and 2. If it's reasonably complete and has tests. Thanks, Justin
Mustella errors
I am trying to get my VM back online. The flex-sdk compiles fine, but when I run ./mini_run -all, I am getting these errors: Any idea? chmod_shells: [echo] changing user shell files to executable shells: BUILD FAILED C:\apacheflex\flex-sdk\mustella\build.xml:1127: The following error occurred while executing this line: C:\apacheflex\flex-sdk\mustella\build.xml:659: Execute failed: java.io.IOException: Cannot run program \cygwin\bin\sh.exe: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:470) at java.lang.Runtime.exec(Runtime.java:593) at org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:41) at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:428) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:442) at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:628) at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669) at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:495) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:440) at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.Main.runBuild(Main.java:851) at org.apache.tools.ant.Main.startAnt(Main.java:235) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(ProcessImpl.java:177) at java.lang.ProcessImpl.start(ProcessImpl.java:28) at java.lang.ProcessBuilder.start(ProcessBuilder.java:452) ... 36 more Total time: 12 seconds
Re: Mustella errors
Never mind, I figured it out. I am using a 64bit version of Cygwin. So, in mustella/build.xml, changing property name=cygwinshell value=/cygwin/bin/sh.exe / to property name=cygwinshell value=/cygwin64/bin/sh.exe / fixed this. Thanks, Om On Mon, Dec 9, 2013 at 6:04 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: I am trying to get my VM back online. The flex-sdk compiles fine, but when I run ./mini_run -all, I am getting these errors: Any idea? chmod_shells: [echo] changing user shell files to executable shells: BUILD FAILED C:\apacheflex\flex-sdk\mustella\build.xml:1127: The following error occurred while executing this line: C:\apacheflex\flex-sdk\mustella\build.xml:659: Execute failed: java.io.IOException: Cannot run program \cygwin\bin\sh.exe: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:470) at java.lang.Runtime.exec(Runtime.java:593) at org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:41) at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:428) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:442) at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:628) at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669) at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:495) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:440) at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at org.apache.tools.ant.Project.executeTarget(Project.java:1364) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1248) at org.apache.tools.ant.Main.runBuild(Main.java:851) at org.apache.tools.ant.Main.startAnt(Main.java:235) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(ProcessImpl.java:177) at java.lang.ProcessImpl.start(ProcessImpl.java:28) at java.lang.ProcessBuilder.start(ProcessBuilder.java:452) ... 36 more Total time: 12 seconds
Re: [Builds/Jenkins] Help and advise needed
I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down... - the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, he feels entitled to use our builds to experiment. I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly. The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects... Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning. Thanks! EdB
Re: [Builds/Jenkins] Help and advise needed
Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly. Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins? Like a command line that he can simply copy-paste into a shell and give us the results from? EdB On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui aha...@adobe.com wrote: I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down... - the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, he feels entitled to use our builds to experiment. I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly. The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not
RE: [Builds/Jenkins] Help and advise needed
Simple yet radical proposition: The pbk shaders didn't evolve much, and the compiled pbj are already committed to the repo (although git history says they have been removed). So couldn't we simply comment/strip pixelbender-compile from the build ? If it ever happens to change, we could then recompile the pbj and recommit. What do you think ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 10 décembre 2013 08:12 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly. Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins? Like a command line that he can simply copy-paste into a shell and give us the results from? EdB On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui aha...@adobe.com wrote: I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: nine is enough. A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones - since the windows1 slave is old, full and overworked, it regularly went down
Re: [Builds/Jenkins] Help and advise needed
On 12/9/13 11:12 PM, Erik de Bruin e...@ixsoftware.nl wrote: Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly. Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins? Like a command line that he can simply copy-paste into a shell and give us the results from? Yeah, it is a pretty simple compiler. All we do is give it a command that is effectively pbutil input output as in: $PIXELBENDER_HOME\pbutil.exe $FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo r.pbk $FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo r.pbj If you have a windows machine please verify that I didn't type that wrong, I'm on my mac right now. I know everyone claims nothing changed. But I'm wondering if we can compare Om's VM setup against yours and fix Om's setup before we go back and bug Gavin. Meanwhile, I'm trying to find the source to the compiler. I have a wild guess that the aif dlls have some silly check for graphic cards or some other Photoshop or After Effects dependency. Or maybe some OpenGL library that comes with newer versions of Windows. If it is a graphics card thing then some hardware change or configuration outside the slave itself could have caused things to fail. Then everyone would technically be right that the nothing changed in the Slave or our code. -Alex EdB On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui aha...@adobe.com wrote: I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on
Re: [Builds/Jenkins] Help and advise needed
We could take the pixel bender compilation out of the jenkins builds, but not our release package. It must contain the source and instructions for building it, and the binary package must contain that compiled source so folks don't have to compile it. The compiled pbj's should not be in the repo. Hopefully they were removed. -Alex On 12/9/13 11:26 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Simple yet radical proposition: The pbk shaders didn't evolve much, and the compiled pbj are already committed to the repo (although git history says they have been removed). So couldn't we simply comment/strip pixelbender-compile from the build ? If it ever happens to change, we could then recompile the pbj and recommit. What do you think ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 10 décembre 2013 08:12 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly. Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins? Like a command line that he can simply copy-paste into a shell and give us the results from? EdB On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui aha...@adobe.com wrote: I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but
RE: [Builds/Jenkins] Help and advise needed
Actually, *.pbj are ignored by git, so the files aren't there, although they were in the past (cf. git log). But the idea is the same. -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mardi 10 décembre 2013 08:27 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed Simple yet radical proposition: The pbk shaders didn't evolve much, and the compiled pbj are already committed to the repo (although git history says they have been removed). So couldn't we simply comment/strip pixelbender-compile from the build ? If it ever happens to change, we could then recompile the pbj and recommit. What do you think ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 10 décembre 2013 08:12 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly. Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins? Like a command line that he can simply copy-paste into a shell and give us the results from? EdB On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui aha...@adobe.com wrote: I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help and advise needed Hi, I'm having some difficulty getting the 'regular' builds on 'build@a.o' working. For those not subscribed to the builds list, the situation is as follows: - there are supposedly 9 admins for the windows1 slave, but only one is sporadically active.
Re: [Builds/Jenkins] Help and advise needed
Apache repos aren't supposed to contain compiled code. The pbj files were removed during the initial release audit. I don't think a workaround can involve checking in the pbj files. But we could borrow them from a prior release package temporarily. -Alex On 12/9/13 11:35 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Actually, *.pbj are ignored by git, so the files aren't there, although they were in the past (cf. git log). But the idea is the same. -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : mardi 10 décembre 2013 08:27 À : dev@flex.apache.org Objet : RE: [Builds/Jenkins] Help and advise needed Simple yet radical proposition: The pbk shaders didn't evolve much, and the compiled pbj are already committed to the repo (although git history says they have been removed). So couldn't we simply comment/strip pixelbender-compile from the build ? If it ever happens to change, we could then recompile the pbj and recommit. What do you think ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 10 décembre 2013 08:12 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly. Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins? Like a command line that he can simply copy-paste into a shell and give us the results from? EdB On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui aha...@adobe.com wrote: I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2 So maybe using \ instead of / could fix the issue ? WDYT? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 08:53 À : dev@flex.apache.org Objet : [Builds/Jenkins] Help
RE: [Builds/Jenkins] Help and advise needed
So we could make the compilation conditional on a env parameter, and set that in the Jenkins job accordingly? Note: the current build has already a condition unless=isLinux. Does this mean Pixel Bender will not compile on Linux machines ? target name=pixelbender-compile unless=isLinux Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 10 décembre 2013 08:33 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed We could take the pixel bender compilation out of the jenkins builds, but not our release package. It must contain the source and instructions for building it, and the binary package must contain that compiled source so folks don't have to compile it. The compiled pbj's should not be in the repo. Hopefully they were removed. -Alex On 12/9/13 11:26 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Simple yet radical proposition: The pbk shaders didn't evolve much, and the compiled pbj are already committed to the repo (although git history says they have been removed). So couldn't we simply comment/strip pixelbender-compile from the build ? If it ever happens to change, we could then recompile the pbj and recommit. What do you think ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 10 décembre 2013 08:12 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly. Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins? Like a command line that he can simply copy-paste into a shell and give us the results from? EdB On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui aha...@adobe.com wrote: I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2 When I run it on my local env, it gives the following: [echo] PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
Re: [Builds/Jenkins] Help and advise needed
On 12/9/13 11:40 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: So we could make the compilation conditional on a env parameter, and set that in the Jenkins job accordingly? Yes, but keep in mind that there is always a chance that someone who does use the pbj's will grab the nightly and complain. Note: the current build has already a condition unless=isLinux. Does this mean Pixel Bender will not compile on Linux machines ? That's correct, we don't have a way to build the pbj files on Linux. target name=pixelbender-compile unless=isLinux Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 10 décembre 2013 08:33 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed We could take the pixel bender compilation out of the jenkins builds, but not our release package. It must contain the source and instructions for building it, and the binary package must contain that compiled source so folks don't have to compile it. The compiled pbj's should not be in the repo. Hopefully they were removed. -Alex On 12/9/13 11:26 PM, Maurice Amsellem maurice.amsel...@systar.com wrote: Simple yet radical proposition: The pbk shaders didn't evolve much, and the compiled pbj are already committed to the repo (although git history says they have been removed). So couldn't we simply comment/strip pixelbender-compile from the build ? If it ever happens to change, we could then recompile the pbj and recommit. What do you think ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 10 décembre 2013 08:12 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly. Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins? Like a command line that he can simply copy-paste into a shell and give us the results from? EdB On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui aha...@adobe.com wrote: I tried to reproduce the failure on my machine but couldn't. I tried different path statements, removing the aif_* dlls, and changing execute rights on those dlls. I did find that the string Internal Exception is in the aif_core.dll. Not sure what to do next, but now I'm thinking: maybe nobody has seen this on their local computers? Only on the Jenkins Windows Slave and Windows VM? What do they have in common? What version of Windows are they running? What kind of graphics cards do they have? -Alex On 12/9/13 11:38 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:56 AM, Alex Harui aha...@adobe.com wrote: Ah, that thread looked like it was a year old. Did you work around it or just stop working on it? I just stopped working on it because I hit a dead end. I was clueless as to how to fix it. Other than checking the path, I don't have any ideas to try at the moment. On your Azure VM, if you manually launch the compiler from Windows command prompt you get this error, right? I will try it out tonight and let you know. Thanks, Om -Alex On 12/9/13 10:48 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Dec 9, 2013 10:35 AM, Alex Harui aha...@adobe.com wrote: We keep hitting this error, but the mail archives do not document how we fix it. This time, we should write down the answer. Om's hit it, Justin hit it, I think I had it once. The emails seem to indicate that it ispath related, but the build.xml does at least check if the pbutil.exe exists and is passing on that. In my case, I have not been able to fix it. In fact, if we are trying to reproduce the problem, we could use my Mustella VM on Azure and see if we can figure out what is happening. We can then apply that fix to the windows1 slave on builds.apache.org Thanks, Om I'll try to see if I can repro on my windows box tonight. -Alex On 12/9/13 12:16 AM, Maurice Amsellem maurice.amsel...@systar.com wrote: Thanks Erik for the clarification. I confirm to you, I had to send the updated swc manually for testing because the nightly build was down. Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something. I can see from the build logs that pixel bender build failed and it seems to be a path issue. If that's correct, this is the path I am using on my local build in my env.properties: env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 I can see that in the build log, the path is: check-pixelbender-home: [echo] PIXELBENDER_HOME is
Re: New Flex MaskedTextInput Spark Component
Nice component, thanks. About the mobile, I had a component with immediate validation (e.g. numeric input), that on mobile does not work because the TextOperationEvent dispatched does not contain the most important information (the operation:FlowOperation attribute). Probably non-TLF implementations used on mobiles only emulates the top-level event, but does not have a way to provide the same level of detail about the operation. 2013/12/10 Justin Mclean jus...@classsoftware.com Hi, @Justin, I'll check your comments to see how we can take into account all this things, but I'm afraid that this initial component is not as smart..maybe with the time and your help we can build such versatile maskedtextinput component. Sure can help out there and tat certainly doesn't need to be done right away. Have a single separator is still useful for a lot of cases. So taking into account that the component is wanted, could you guys point me to the place where I could make a first commit? Two main choices: 1. in frameworks/projects/experimental 2. in frameworks/projects/apache I'd go with 1. if you think it still needs a bit of work or is missing tests and 2. If it's reasonably complete and has tests. Thanks, Justin
