flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Dove <greg.d...@gmail.com>
Subject Re: [Falcon] Quick sanity check - I am getting timeouts on compiler-jx tests
Date Thu, 21 Jul 2016 03:54:48 GMT
Thanks Alex.

It actually runs about 25% faster when I set fork="no" on the junit task
which seems odd to me.
This is on windows 10. The whole 'ant all' build from flex-asjs used to
take around 8-9 mins, and now takes 17 mins.
I must have inadvertently changed something in my setup somewhere to cause
this, perhaps it is related to ant version or something like that.
I'll come back to it later, for now at least I can get it to complete.

On Thu, Jul 21, 2016 at 9:13 AM, Alex Harui <aharui@adobe.com> wrote:

> They run in a few minutes on my Mac.  I've found that on occasion memory
> gets low or maybe some other variable changes and the tests slow way down
> because a new VM is launched for every test and that seems to take a long
> time.
> HTH,
> -Alex
> On 7/20/16, 1:26 PM, "Greg Dove" <greg.dove@gmail.com> wrote:
> >Can someone please let me know how long the compiler.jx.tests normally
> >take
> >to run. I am getting timeouts, this is probably related to the speed of my
> >dev machine I'm guessing. If I bump test.timeout to 600000 (10 mins) they
> >complete in around 8 mins.
> >
> >This happens to me on develop branch builds. I suspect it's just my
> >machine, but wanted to make sure it's not some recent change in the code,
> >because I *thought* these used to be much faster.
> >
> >thanks
> >-Greg

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message