I was finally able to upgrade to 3.9.4 (some internal maven dependencies had to be fixed to allow this). They appear to be working when running more then one test (JBEHAVE-1046 <https://jira.codehaus.org/browse/JBEHAVE-1046> is preventing us from running just a single test)
Thanks for fixing this, and all of your hard work! On Mon, Aug 25, 2014 at 3:18 PM, Mauro Talevi <mauro.tal...@aquilonia.org> wrote: > Try with latest releases: 3.9.4 or 4.0-beta-10. > > > On 25/08/2014 21:03, Brent Barker wrote: > > Thanks for looking into that! > > I tried the latest snapshot. However, it still doesn't appear that all of > the times are correct. The total time on the report is close to the entire > execution time. > > I would think the total time in the report to be significantly greater > then the actual execution time. It appears the time for each thread isn't > being fully accounted for. Some stories that take a long time still look > like they have a 0 second execution time, but running a couple of stories > the report looks correct. > > I'll try to get a example project put together. > > > On Wed, Aug 20, 2014 at 1:10 AM, Mauro Talevi <mauro.tal...@aquilonia.org> > wrote: > >> Reproduced and fixed: https://jira.codehaus.org/browse/JBEHAVE-1041 >> >> Can you try out latest snapshot? >> >> >> On 11/08/2014 18:10, Brent Barker wrote: >> >>> Hi, >>> When executing reports in multiple threads, the execution times are not >>> correct. Instead of varying from 1-10 minutes, they say the execute in >>> microseconds (which i know is not the case) >>> >>> Are other seeing this? >>> Thanks >>> -Brent >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > >
