Build failed in Jenkins: flex-sdk_mustella-mobile #14

See -- [...truncated 21499 lines...] [java] mobile/components/CheckBox/styles/checkbox_styles Mobile_checkbox_styles_decrease_letterSpacing_iconPlacement_top Failed CompareBitmap(body:step 5) B

Build failed in Jenkins: flex-sdk_mustella-mobile #13

See -- [...truncated 22183 lines...] [java] mobile/components/CheckBox/properties/checkbox_properties Mobile_CheckBox_height_increase Failed CompareBitmap(body:step 3) Baseline image could not

Build failed in Jenkins: flex-sdk_mustella-air #9

See -- [...truncated 7408 lines...] [java] After Wait loop 18:38:32.654 waiting = 0 [java] clobberProcess false [java] Total Results so far: 25 [java] removing the xml app file [ja

Build failed in Jenkins: flex-sdk_mustella #190

See Changes: [erik] Explicitly exit with an error code when there are failures left after running with '-failures'… Without this code the script 'jenkins.sh' will complete successfully - as nothing went wrong with it - and Jenkins won't

Re: [FlexJS][FalconJX] The Beginnings of Databinding

Good catch. Fixed. Thanks,-Alex On 6/28/13 3:24 PM, "OmPrakash Muppirala" wrote: >Sure thing. > >I still see that active development branch pointing to SVN which shows the >last activity at a few months back. Can you fix that to point to the new >git repos? > >Om > >On Fri, Jun 28, 2013 at 3:

Re: [FlexJS][FalconJX] The Beginnings of Databinding

Sure thing. I still see that active development branch pointing to SVN which shows the last activity at a few months back. Can you fix that to point to the new git repos? Om On Fri, Jun 28, 2013 at 3:14 PM, Alex Harui wrote: > OK, made some updates to the wiki. Thanks for reminding me to upd

Re: [FlexJS][FalconJX] The Beginnings of Databinding

OK, made some updates to the wiki. Thanks for reminding me to update what was there. I hadn't realized it was so stale. -Alex On 6/28/13 2:25 PM, "OmPrakash Muppirala" wrote: >Just did it. > >If you can update the links and the breaking news section of the page here >[1], that would be great.

Re: [FlexJS][FalconJX] The Beginnings of Databinding

Just did it. If you can update the links and the breaking news section of the page here [1], that would be great. Thanks, Om [1] https://cwiki.apache.org/confluence/display/FLEX/Alex's+FlexJS+Prototype On Fri, Jun 28, 2013 at 2:04 PM, Alex Harui wrote: > OK with me. > > On 6/28/13 1:58 PM, "O

Re: [FlexJS][FalconJX] The Beginnings of Databinding

OK with me. On 6/28/13 1:58 PM, "OmPrakash Muppirala" wrote: >Do you mind if I put out an official tweet about this? > >Om > >On Wed, Jun 26, 2013 at 6:51 AM, Alex Harui wrote: > >> Sorry, forgot to mention that the FlexJSOverlay is updated on [1] >> and examples are at [2] with view source ena

Re: [FlexJS][FalconJX] The Beginnings of Databinding

Do you mind if I put out an official tweet about this? Om On Wed, Jun 26, 2013 at 6:51 AM, Alex Harui wrote: > Sorry, forgot to mention that the FlexJSOverlay is updated on [1] > and examples are at [2] with view source enabled for the Flash versions. > > [1] http://people.apache.org/~aharui/Fl

Build failed in Jenkins: flex-sdk_mustella-mobile #12

See -- [...truncated 21893 lines...] [java] mobile/components/RadioButton/properties/radiobutton_properties Mobile_RadioButton_height_increase Failed CompareBitmap(body:step 3) Baseline image c

Re: Mustella VM emails to 'issues'?

On 6/28/13 12:32 AM, "Erik de Bruin" wrote: >Hi, > >I was just wondering: would it be better if I have Jenkins send the >Mustella run emails to 'issues@'? Wouldn't commits@ be better? > >The way it stands now, all three runs (main, AIR and mobile) have >tests failing (even after -failures). Th

Build failed in Jenkins: flex-sdk_asdoc #51

See -- [...truncated 1714 lines...] automation_agent_bundles-clean: automation_agent_bundles-clean: automation_agent_bundles-clean: automation_agent_bundles-clean: automation_agent_bundles-clean: autom

Re: [LAZY] delete obsolete Jenkins jobs

On Jun 28, 2013 5:36 AM, "Erik de Bruin" wrote: > > Ah, I see the confusion. This has nothing to do with the Mustella VM > and don't want to wipe ALL jobs on builds@a.o, just the old jobs that > were there before I created the current set. > > The current set is: > > flex-falcon > flex-flexunit >

Re: [LAZY] delete obsolete Jenkins jobs

Hi, > Ah, I see the confusion. No issues here - feel free to nuke them from orbit. Justin

Re: Build failed in Jenkins: flex-sdk_asdoc #49

It's probably in the garbage. Get it quickly, before they collect it. :-P EdB On Fri, Jun 28, 2013 at 2:52 PM, Kessler CTR Mark J wrote: > While you're at it, find where I've left mine. I've been missing my memory > for some time now lol. > > -Original Message- > From: Erik de Bruin

RE: Build failed in Jenkins: flex-sdk_asdoc #49

While you're at it, find where I've left mine. I've been missing my memory for some time now lol. -Original Message- From: Erik de Bruin [mailto:e...@ixsoftware.nl] Sent: Friday, June 28, 2013 8:40 AM To: dev@flex.apache.org Subject: Re: Build failed in Jenkins: flex-sdk_asdoc #49 Yeah

Jenkins build is back to normal : flex-sdk_asdoc #50

See

Re: Build failed in Jenkins: flex-sdk_asdoc #49

Yeah... it does seem to happen only every once in a blue moon, though. I'm running the job again, see if the machine remembers where it left it's memory. EdB On Fri, Jun 28, 2013 at 1:34 PM, Kessler CTR Mark J wrote: > Guess there is not much fixing this without having added memory. > > "[

Re: [LAZY] delete obsolete Jenkins jobs

Ah, I see the confusion. This has nothing to do with the Mustella VM and don't want to wipe ALL jobs on builds@a.o, just the old jobs that were there before I created the current set. The current set is: flex-falcon flex-flexunit flex-sdk flex-sdk_release flex-sdk_asdoc flex-tlf The old set (tha

Re: [LAZY] delete obsolete Jenkins jobs

Hi, > If no-one objects within three days, I'll assume lazy consensus and remove > them. I'd just stop and wipe the workspaces rather than removing them just in case they are needed again. As they are on Apache infrastructure they are likely to be around for some time. No offence intended but

RE: Build failed in Jenkins: flex-sdk_asdoc #49

Guess there is not much fixing this without having added memory. "[asdoc] Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded" -Mark -Original Message- From: Apache Jenkins Server [mailto:jenk...@builds.apache.org] Sent: Friday, June 28, 2013 7:15 AM T

Build failed in Jenkins: flex-sdk_asdoc #49

See Changes: [erik] Explicitly exit with an error code when there are failures left after running with '-failures'… Without this code the script 'jenkins.sh' will complete successfully - as nothing went wrong with it - and Jenkins won't

Jenkins build is back to normal : flex-sdk_release #54

See

Build failed in Jenkins: flex-sdk_mustella-mobile #11

See -- [...truncated 24146 lines...] [java] mobile/components/TextArea/Styles/TextArea_styles_tester TextArea_leading_test2 Failed CompareBitmap(body:step 3) compare returned-3 [java] mobi

[LAZY] delete obsolete Jenkins jobs

Hi, On the builds@a.o machine there are 7 old Jenkins jobs. These jobs are previous versions of the current set. Most if not all 'features' in the old jobs are implemented in the current ones. I suggest we clean them up (remove them) in order to keep from cluttering the Jenkins instance with lots

Re: Are we "nerd" driven or "business realistic" driven?

Hi, > Folks, I've decided to reedit that post on Spicefactory. It was created in a > hurry and with a certain amount of (maybe unnecessary) bitterness in mind. > Since it's public, it certainly doesn't help Apache Flex perception. These > opinions should be presented and voiced internally on th

Re: Are we "nerd" driven or "business realistic" driven?

> I assume you prefer a web forum style? I find web forums slow, buggy, slow > and hard to search on, hard to use on mobile devices and assume you're always > have a connection. Each to their own. I'd say so, yes. >> - arm Flex beautifully for mobile. > What do you need needs to be one her

Build failed in Jenkins: flex-sdk_mustella-air #8

See -- [...truncated 7546 lines...] [java] apollo adj thinks it's a swf [java] writing Apollo file! [java] full swf is C:\jenkins_slave\workspace\flex-sdk_mustella-air\mustella\tests\apollo

Re: Parallel Mustella runs

I had to give them a card reference to get started (companies seem obsessed by this), but I made sure the "Spending Limit" option remained in place and set to 0 euro. This way the worst case scenario is that if I run out of 'free' credits before the month ends, my services will be suspended, but no

Build failed in Jenkins: flex-sdk_release #53

See Changes: [erik] Explicitly exit with an error code when there are failures left after running with '-failures'… Without this code the script 'jenkins.sh' will complete successfully - as nothing went wrong with it - and Jenkins won'

Re: Parallel Mustella runs

Ok, I checked better and it should be 1 x M = 2 UC x 1,6 GHz, 3,5 GB RAM = €99,74/mo, so it should fit into the offered 115 euro/month, what is weird is they're asking me for a credit card reference, I just don't want to be charged, I think to remember you talk about it but can't find the email

Re: Mustella VM emails to 'issues'?

Hi, > I was just wondering: would it be better if I have Jenkins send the > Mustella run emails to 'issues@'? +0 from me. Someone may break the build and not be aware of it, but if others think that's OK go ahead, I guess someone could politely point it out and suggest they subscribe to issues@

Jenkins build is back to normal : flex-sdk_mustella-air #7

See

Mustella VM emails to 'issues'?

Hi, I was just wondering: would it be better if I have Jenkins send the Mustella run emails to 'issues@'? The way it stands now, all three runs (main, AIR and mobile) have tests failing (even after -failures). This means that per full run, three emails will be sent... twice a day. That will put e

Re: Parallel Mustella runs

Actually, MS just changed the way they "charge" for the MSDN accounts, they now work with credits. Currently my account has 115 euro/month credit and - as far as I can tell, this is a recent change - running a Medium VM (2 x 1.6GHz CPU, 3.5GB RAM) for a month will just fit that credit. A Medium VM