Re: Next Flex SDK release

The new code had a successful build on the CI machine. The difference in the build time is less than I would have thought it would be. It looks like the tests are taking about 2 minutes less than they used to.[1] I guess that’s something, but I’m not sure it’s different enough for a general

Re: Next Flex SDK release

On 12/10/15, 4:13 AM, "Harbs" wrote: >The new code had a successful build on the CI machine. The difference in >the build time is less than I would have thought it would be. It looks >like the tests are taking about 2 minutes less than they used to.[1] > >I guess that’s

Re: Next Flex SDK release

OK. This is now fixed. Anyone have thoughts on performance checking to ensure that future performance degradation is caught? On Nov 18, 2015, at 7:53 AM, Alex Harui wrote: > 2) TLF Performance > https://issues.apache.org/jira/browse/FLEX-34769 > > I’d like to get an update

RE: Next Flex SDK release

thank you so freaking much for this one Harbs! -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Wednesday, December 09, 2015 2:38 PM To: dev@flex.apache.org Subject: Re: Next Flex SDK release OK. This is now fixed. Anyone have thoughts on performance checking

RE: Next Flex SDK release

nvm, saw your notes, didn't realize 4.9 was that fast! -Original Message- From: Jason Taylor [mailto:ja...@dedoose.com] Sent: Wednesday, December 09, 2015 3:22 PM To: dev@flex.apache.org Subject: RE: Next Flex SDK release Harbs, Flex SDK 13.0 was the last release where TLF worked

Re: Next Flex SDK release

Hi, > Anyone have thoughts on performance checking to ensure that future > performance degradation is caught? Usually I just add a couple of unit tests that assert the time run < some reasonable value. No idea how easy that is to do in this case. Thanks, Justin

RE: Next Flex SDK release

@flex.apache.org Subject: Re: Next Flex SDK release It looks like I don't need 4.6. There's a 3.0 branch in the Git repo which seems to have ti working correctly. On Dec 7, 2015, at 3:19 PM, Harbs <harbs.li...@gmail.com> wrote: > OK. I'm working on this, and I just added a comment to the JIR

Re: Mustella fixing (was Re: Next Flex SDK release)

On 12/8/15, 2:57 AM, "Kessler CTR Mark J" wrote: >If I remember correctly one of the main reasons we started embedding >fonts was to be able to rotate text on reports. The other being a >consistent font no matter the platform/browser. We had to embed a normal

RE: Mustella fixing (was Re: Next Flex SDK release)

fonts, we have 4 declarations in our css. With / without CFF for both the regular font and bold font. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, December 08, 2015 11:11 AM To: dev@flex.apache.org Subject: Re: Mustella fixing (was Re: Next Flex SDK

Re: Mustella fixing (was Re: Next Flex SDK release)

On 24/11/15 19:00, OmPrakash Muppirala wrote: And do you think I can close this issue as fixed for now? The Mustella tests are still failing... Tom

Re: Next Flex SDK release

It looks like I don’t need 4.6. There’s a 3.0 branch in the Git repo which seems to have ti working correctly. On Dec 7, 2015, at 3:19 PM, Harbs wrote: > OK. I’m working on this, and I just added a comment to the JIRA with my > preliminary observations. Kind of

RE: Mustella fixing (was Re: Next Flex SDK release)

issues more frequently. Right now it looks like the majority of the failures are bitmap comparisons. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, December 07, 2015 11:24 AM To: dev@flex.apache.org Subject: Re: Mustella fixing (was Re: Next Flex

Re: Next Flex SDK release

OK. I’m working on this, and I just added a comment to the JIRA with my preliminary observations. Kind of interesting... I’m going to need to find the source of the old TLF to compare. I don’t want to use 4.9.1 because that code just had a band-aid. I assume Adobe's 4.6 code was working

Re: Mustella fixing (was Re: Next Flex SDK release)

I’ve never used charts, so I have no idea about RTL and the like. What was the issue with Spark? What about using Twitter to try and find out if anyone is using Spark Label in charts? Harbs On Nov 24, 2015, at 7:12 PM, Alex Harui wrote: > > > On 11/24/15, 12:06 AM,

Re: Mustella fixing (was Re: Next Flex SDK release)

On 11/24/15, 9:24 AM, "Harbs" wrote: >I’ve never used charts, so I have no idea about RTL and the like. What >was the issue with Spark? Back in July, I took a look [1] and it appeared that Charts used a TextField instead of a Spark Label to measure how much room there

Re: Mustella fixing (was Re: Next Flex SDK release)

On 11/24/15, 12:06 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Mon, Nov 23, 2015 at 11:54 PM, Alex Harui wrote: > >> >> >> I decided to take a quick peek. It looks like a change was made to have >>

Re: Mustella fixing (was Re: Next Flex SDK release)

That's good to know. Can you please update this ticket with your comments so that we can go back and easily find it when such an issue arises in the future? https://issues.apache.org/jira/browse/FLEX-34909 And do you think I can close this issue as fixed for now? Thanks, Om On Tue, Nov 24,

Re: Mustella fixing (was Re: Next Flex SDK release)

On Mon, Nov 23, 2015 at 11:54 PM, Alex Harui wrote: > > > On 11/20/15, 9:05 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" > wrote: > > >>I took a look at one of the bad.png files from Charts and the fonts were >

Re: Mustella fixing (was Re: Next Flex SDK release)

On 11/20/15, 9:05 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >>I took a look at one of the bad.png files from Charts and the fonts were >> rendering differently, although I also think I saw a small difference in >> the

Re: Mustella fixing (was Re: Next Flex SDK release)

On Nov 19, 2015 11:34 PM, "Alex Harui" wrote: > > Looks like Tom also has the magic, although I did reboot the server as > well to get past the repo access errors, but rebooting in the past wasn't > enough. > > Air and Mobile are passing, and I would say the SDK errors are

Mustella fixing (was Re: Next Flex SDK release)

OK. The last run failed, and was not in progress. I ran all four players in that folder and closed them. Let's see what happens on the next run Tom On 18/11/15 22:52, Alex Harui wrote: The mustella server has caught legitimate issues, most recently with some sort behavior changes. But yeah,

Re: Mustella fixing (was Re: Next Flex SDK release)

Looks like Tom also has the magic, although I did reboot the server as well to get past the repo access errors, but rebooting in the past wasn't enough. Air and Mobile are passing, and I would say the SDK errors are probably real errors: There are some Sort errors left over from some changes we

RE: Next Flex SDK release

I meant to go back and look at that one a while ago, guess it fell off my radar. I'll have a look at it tonight. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, November 18, 2015 12:53 AM To: dev@flex.apache.org Subject: Re: Next Flex SDK release

Re: Next Flex SDK release

I've never seen a 'real' failure. It always seems to be Mustella screwing itself up. I don't have a Windows machine to chase them down with. Tom On 18/11/15 07:22, Justin Mclean wrote: Hi, The flex-sdk_mustella Jenkin's task does not currently pass: http://flex-mustella.cloudapp.net/

Re: Next Flex SDK release

On 11/15/15, 9:11 PM, "Justin Mclean" wrote: >Hi, > >Now the FlexJS releases are just about to be announced, I think it's >about time we made a Flex SDK release as the previous one was released >was way back in March. > >Unless anyone else want to give it a go I’ll act

Re: Next Flex SDK release

The flex-sdk_mustella Jenkin's task does not currently pass: http://flex-mustella.cloudapp.net/ Tom On 16/11/15 05:11, Justin Mclean wrote: Is there any regression issues in 4.14/4.14.1 that anyone feels needs to be addressed before making a new release?

Re: Next Flex SDK release

Hi, > The flex-sdk_mustella Jenkin's task does not currently pass: > http://flex-mustella.cloudapp.net/ Does anyone know if the machine just need a bit of maintaince or are these do to real failures? I can see that the RC jobs have not run successfully for 7

Re: Next Flex SDK release

Hi, The JIRA (and sib tasks) for the next release can be found here [1], if you want to help out please assign yourself one of the subtasks. I’ve had a go at the contributors list and the fixed bugs, if anyone want to review the changes that would be a great help. Thanks, Justin 1.

Re: Next Flex SDK release

You had created such a flag, but enabling it causes lots of RTEs with the current code. I’d rather find the underlying cause of the problem which seems to be way too much recursion. I will try to take another look at this issue next week. On Nov 18, 2015, at 7:53 AM, Alex Harui