You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Greg Dove <gr...@gmail.com> on 2016/07/20 20:26:02 UTC
[Falcon] Quick sanity check - I am getting timeouts on compiler-jx tests
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
Re: [Falcon] Quick sanity check - I am getting timeouts on
compiler-jx tests
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Really cool Chris, I already did not follow yet, but I'll do soon.
I could suggest to make another page as a follow up with simple steps for
people creating a project from scratch with mavenized FlexJS , since create
a basic pom, and so on...
I think better if it was IDE oriented (and I'll suggest IntelliJ)
Thanks!
Carlos
2016-07-21 22:51 GMT+02:00 Greg Dove <gr...@gmail.com>:
> The how-to seems real easy :) I will give it a try later today!
>
> And my original issue with the timeouts somehow fixed itself today, those
> tests complete in under a minute now! I forgot the golden rule of Windows:
> If something doesn't work right, try a reboot.
>
> On Thu, Jul 21, 2016 at 9:34 PM, Christofer Dutz <
> christofer.dutz@c-ware.de>
> wrote:
>
> > Ok ... just finished the how-to:
> >
> >
> https://cwiki.apache.org/confluence/display/FLEX/Building+FlexJS+with+Maven
> >
> > I'd appreciate feedback ;-)
> >
> >
> > Chris
> >
> > ________________________________
> > Von: Greg Dove <gr...@gmail.com>
> > Gesendet: Donnerstag, 21. Juli 2016 08:56:53
> > An: dev@flex.apache.org
> > Betreff: Re: [Falcon] Quick sanity check - I am getting timeouts on
> > compiler-jx tests
> >
> > The forkMode is perBatch not perTest so that 'sounds like' (I am unsure!)
> > that shouldn't have such a big impact.
> > I had thought this was definitely much faster previously so I think
> > something might have changed on my side. I do see an additional Java
> > process being started, but it sits at 0% cpu, so not really sure what is
> > going on. But I'm not too worried for now as I don't run these often
> > (although I am messing a bit with the compiler code to see what I can get
> > my head around).
> >
> > I am open to trying Maven, will be happy to check out the how-to when
> it's
> > ready. I have never used Maven before... only ant.
> >
> > cheers,
> > Greg
> >
> >
> > On Thu, Jul 21, 2016 at 6:47 PM, Christofer Dutz <
> > christofer.dutz@c-ware.de>
> > wrote:
> >
> > > without fork the build doesn't have to create a new vm for every test.
> > > This is a huge performance improvement. You could also give the Maven
> > build
> > > a try ... This seems to be a lot faster :-)
> > >
> > > I'm currently working on a how-to doc on that.
> > >
> > > Chris
> > >
> > >
> > >
> > > Von meinem Samsung Galaxy Smartphone gesendet.
> > >
> > >
> > > -------- Ursprüngliche Nachricht --------
> > > Von: Greg Dove <gr...@gmail.com>
> > > Datum: 21.07.16 05:54 (GMT+01:00)
> > > An: dev@flex.apache.org
> > > Betreff: Re: [Falcon] Quick sanity check - I am getting timeouts on
> > > compiler-jx tests
> > >
> > > 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 <ah...@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" <gr...@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
> > > >
> > > >
> > >
> >
>
--
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
Re: [Falcon] Quick sanity check - I am getting timeouts on
compiler-jx tests
Posted by Greg Dove <gr...@gmail.com>.
The how-to seems real easy :) I will give it a try later today!
And my original issue with the timeouts somehow fixed itself today, those
tests complete in under a minute now! I forgot the golden rule of Windows:
If something doesn't work right, try a reboot.
On Thu, Jul 21, 2016 at 9:34 PM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Ok ... just finished the how-to:
>
> https://cwiki.apache.org/confluence/display/FLEX/Building+FlexJS+with+Maven
>
> I'd appreciate feedback ;-)
>
>
> Chris
>
> ________________________________
> Von: Greg Dove <gr...@gmail.com>
> Gesendet: Donnerstag, 21. Juli 2016 08:56:53
> An: dev@flex.apache.org
> Betreff: Re: [Falcon] Quick sanity check - I am getting timeouts on
> compiler-jx tests
>
> The forkMode is perBatch not perTest so that 'sounds like' (I am unsure!)
> that shouldn't have such a big impact.
> I had thought this was definitely much faster previously so I think
> something might have changed on my side. I do see an additional Java
> process being started, but it sits at 0% cpu, so not really sure what is
> going on. But I'm not too worried for now as I don't run these often
> (although I am messing a bit with the compiler code to see what I can get
> my head around).
>
> I am open to trying Maven, will be happy to check out the how-to when it's
> ready. I have never used Maven before... only ant.
>
> cheers,
> Greg
>
>
> On Thu, Jul 21, 2016 at 6:47 PM, Christofer Dutz <
> christofer.dutz@c-ware.de>
> wrote:
>
> > without fork the build doesn't have to create a new vm for every test.
> > This is a huge performance improvement. You could also give the Maven
> build
> > a try ... This seems to be a lot faster :-)
> >
> > I'm currently working on a how-to doc on that.
> >
> > Chris
> >
> >
> >
> > Von meinem Samsung Galaxy Smartphone gesendet.
> >
> >
> > -------- Ursprüngliche Nachricht --------
> > Von: Greg Dove <gr...@gmail.com>
> > Datum: 21.07.16 05:54 (GMT+01:00)
> > An: dev@flex.apache.org
> > Betreff: Re: [Falcon] Quick sanity check - I am getting timeouts on
> > compiler-jx tests
> >
> > 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 <ah...@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" <gr...@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
> > >
> > >
> >
>
AW: [Falcon] Quick sanity check - I am getting timeouts on
compiler-jx tests
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok ... just finished the how-to:
https://cwiki.apache.org/confluence/display/FLEX/Building+FlexJS+with+Maven
I'd appreciate feedback ;-)
Chris
________________________________
Von: Greg Dove <gr...@gmail.com>
Gesendet: Donnerstag, 21. Juli 2016 08:56:53
An: dev@flex.apache.org
Betreff: Re: [Falcon] Quick sanity check - I am getting timeouts on compiler-jx tests
The forkMode is perBatch not perTest so that 'sounds like' (I am unsure!)
that shouldn't have such a big impact.
I had thought this was definitely much faster previously so I think
something might have changed on my side. I do see an additional Java
process being started, but it sits at 0% cpu, so not really sure what is
going on. But I'm not too worried for now as I don't run these often
(although I am messing a bit with the compiler code to see what I can get
my head around).
I am open to trying Maven, will be happy to check out the how-to when it's
ready. I have never used Maven before... only ant.
cheers,
Greg
On Thu, Jul 21, 2016 at 6:47 PM, Christofer Dutz <ch...@c-ware.de>
wrote:
> without fork the build doesn't have to create a new vm for every test.
> This is a huge performance improvement. You could also give the Maven build
> a try ... This seems to be a lot faster :-)
>
> I'm currently working on a how-to doc on that.
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> -------- Ursprüngliche Nachricht --------
> Von: Greg Dove <gr...@gmail.com>
> Datum: 21.07.16 05:54 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: [Falcon] Quick sanity check - I am getting timeouts on
> compiler-jx tests
>
> 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 <ah...@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" <gr...@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
> >
> >
>
Re: [Falcon] Quick sanity check - I am getting timeouts on
compiler-jx tests
Posted by Greg Dove <gr...@gmail.com>.
The forkMode is perBatch not perTest so that 'sounds like' (I am unsure!)
that shouldn't have such a big impact.
I had thought this was definitely much faster previously so I think
something might have changed on my side. I do see an additional Java
process being started, but it sits at 0% cpu, so not really sure what is
going on. But I'm not too worried for now as I don't run these often
(although I am messing a bit with the compiler code to see what I can get
my head around).
I am open to trying Maven, will be happy to check out the how-to when it's
ready. I have never used Maven before... only ant.
cheers,
Greg
On Thu, Jul 21, 2016 at 6:47 PM, Christofer Dutz <ch...@c-ware.de>
wrote:
> without fork the build doesn't have to create a new vm for every test.
> This is a huge performance improvement. You could also give the Maven build
> a try ... This seems to be a lot faster :-)
>
> I'm currently working on a how-to doc on that.
>
> Chris
>
>
>
> Von meinem Samsung Galaxy Smartphone gesendet.
>
>
> -------- Ursprüngliche Nachricht --------
> Von: Greg Dove <gr...@gmail.com>
> Datum: 21.07.16 05:54 (GMT+01:00)
> An: dev@flex.apache.org
> Betreff: Re: [Falcon] Quick sanity check - I am getting timeouts on
> compiler-jx tests
>
> 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 <ah...@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" <gr...@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
> >
> >
>
AW: [Falcon] Quick sanity check - I am getting timeouts on
compiler-jx tests
Posted by Christofer Dutz <ch...@c-ware.de>.
without fork the build doesn't have to create a new vm for every test. This is a huge performance improvement. You could also give the Maven build a try ... This seems to be a lot faster :-)
I'm currently working on a how-to doc on that.
Chris
Von meinem Samsung Galaxy Smartphone gesendet.
-------- Ursprüngliche Nachricht --------
Von: Greg Dove <gr...@gmail.com>
Datum: 21.07.16 05:54 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: [Falcon] Quick sanity check - I am getting timeouts on compiler-jx tests
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 <ah...@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" <gr...@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
>
>
Re: [Falcon] Quick sanity check - I am getting timeouts on
compiler-jx tests
Posted by Greg Dove <gr...@gmail.com>.
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 <ah...@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" <gr...@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
>
>
Re: [Falcon] Quick sanity check - I am getting timeouts on
compiler-jx tests
Posted by Alex Harui <ah...@adobe.com>.
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" <gr...@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