Hey Chris,

Awesome! I'll give it a test run.

'll keep u posted.

Thx!

Bert

On Wednesday, September 5, 2012 8:13:19 PM UTC+2, Christofer Dutz wrote:
>
> Hi Bert, 
>
> I think I might have some good news for you. In the course of fixing 
> flexunit4 parametrized tests, I had to refactor allmost all of the 
> test runners. In the old version the SocketReporter was responsible 
> for deciding when a test is finished, in my updated version this is 
> now the responsibility of the test-runner. Hopefully your problem is 
> fixed in the 5.x trunk ... could you give that a try? I committed the 
> stuff yesterday ;-) 
>
> Chris 
>
>
>
> 2012/9/5 Marvin Froeder <[email protected] <javascript:>>: 
> > Take a look on maven docs, the timeouts are configurable, but I do not 
> > recall the configuration names. 
> > 
> > On Sep 5, 2:53 pm, Bert Vandamme <[email protected]> wrote: 
> >> Hey Chris, 
> >> 
> >> We were able to make some progress the issues we were having. 
> >> After further investigation, the order of the mentioned sequence wasn't 
> the 
> >> root cause of the timeouts. (reproduced the issue either way...) 
> >> 
> >> We noticed that some of our tests were started, got the (air-) runtime 
> in 
> >> infinite waiting loop (because the "canClose" property stayed false), 
> and 
> >> were never finished. 
> >> Running every test separately never caused problems, only when they 
> were 
> >> part of a larger test suite. 
> >> 
> >> All of those tests (no async ones) had mocked UIComponents (mockolate), 
> >> which were a huge runtime performance hit, and were probably causing 
> the 
> >> timeouts and test "hangs" when running "big" test suites. 
> >> (I know, mocking concrete instances is a no-no, but the lack of 
> interfaces 
> >> in the flex framework kind-of gave us no option...) 
> >> 
> >> All tests have been running smoothly after replacing those mock objects 
> >> with their actual counterparts. 
> >> 
> >> Thinking of the timeouts and infinite test loops, is there any way that 
> FM 
> >> can run into trouble while running "bloated" tests as described above? 
> >> 
> >> Cheers, 
> >> 
> >> Bert 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> On Wednesday, September 5, 2012 4:37:38 PM UTC+2, Christofer Dutz 
> wrote: 
> >> 
> >> > Sorry guys, 
> >> 
> >> > I coulnd't dig into this issue yet as I was trying to finish some 
> >> > flexunit4 stuff prior to releasing Flexmojos 5.1. 
> >> > I have encountered one other place where there might be 
> race-condition 
> >> > issues when using a fdk greater than 4.5.1. 
> >> > Unfortunately I am completely swamped with work but am hoping to 
> spare 
> >> > some time in about two weeks. 
> >> 
> >> > Chris 
> >> 
> >> > 2012/9/5 Bert Vandamme <[email protected] <javascript:>>: 
> >> > > Hi, 
> >> 
> >> > > Any update on this issue? 
> >> > > We're having similar issues running our unit tests (reproducible on 
> >> > local 
> >> > > machine (windows 7 x64) and on jenkins running on windows server 
> (x32) 
> >> 
> >> > > I've noticed the same sequence causing time-outs. 
> >> 
> >> > > Cheers, 
> >> 
> >> > > Bert 
> >> 
> >> > > On Thursday, August 23, 2012 9:02:32 AM UTC+2, Yennick Trevels 
> wrote: 
> >> 
> >> > >> Yes, so basically this sequence works: 
> >> 
> >> > >> [org.sonatype.flexmojos.test.monitor.AsVmPing] opened server 
> socket on 
> >> > >> port 49257 
> >> 
> >> > >> [DEBUG] [LAUNCHER] ASVmLauncher starting 
> >> > >> [DEBUG] [DEBUG] 
> [org.sonatype.flexmojos.test.monitor.ResultHandler] 
> >> > opened 
> >> > >> server socket on port 39373 
> >> 
> >> > >> and this sequence doesn't: 
> >> 
> >> > >> [DEBUG] [LAUNCHER] ASVmLauncher starting 
> >> > >> [DEBUG] [DEBUG] 
> [org.sonatype.flexmojos.test.monitor.ResultHandler] 
> >> > opened 
> >> > >> server socket on port 39373 
> >> > >> [org.sonatype.flexmojos.test.monitor.AsVmPing] opened server 
> socket on 
> >> > >> port 49257 
> >> 
> >> > > -- 
> >> > > You received this message because you are subscribed to the Google 
> >> > > Groups "Flex Mojos" group. 
> >> > > To post to this group, send email to 
> >> > > [email protected]<javascript:> 
>
> >> > > To unsubscribe from this group, send email to 
> >> > > [email protected] <javascript:> 
> >> > > For more options, visit this group at 
> >> > >http://groups.google.com/group/flex-mojos 
> >> 
> >> > >http://flexmojos.sonatype.org/ 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "Flex Mojos" group. 
> > To post to this group, send email to [email protected]<javascript:> 
> > To unsubscribe from this group, send email to 
> > [email protected] <javascript:> 
> > For more options, visit this group at 
> > http://groups.google.com/group/flex-mojos 
> > 
> > http://flexmojos.sonatype.org/ 
>

-- 
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos

http://flexmojos.sonatype.org/

Reply via email to