[news.eclipse.tools.hyades] Re: issue with the results

[curtispd@xxxxxxxxxx (Curtis d\'Entremont)]

You mean the profiling data you get back is incorrect? i.e. it says it 
took 150s but in reality it took 0.1s ?  I doubt this would fix the 
problem, but if you're running out of options you can try running the 
junit test normally and attaching the profiler to it, rather than 
launching with the profiler. To do this, run the junit test normally with 
the "-XrunpiAgent:server=controlled" VM argument. When you launch, nothing 
will happen - it's waiting for a profiler to attach before continuing. To 
attach, create a new Attach - Java Process launch configuration in 
profiling mode (click Profile... toolbar button). Find the agent 
corresponding to the correct process ID (there'll probably only be one), 
then hit Profile. Once you start monitoring the agent, the VM will start 
running the junit test and collect data.

One more thing to consider - the JVM that is used by the agent controller 
may be different than the one you're using in eclipse. So launching the 
same junit test in run and profile mode might use different JVMs. It 
depends how the agent controller is configured. To set the JVM, run the 
SetConfig script and it will ask you for the JVM.

Thanks,
Curt

fabrice wrote:

> Hi,

> I can start a profiling (Junit test) but the profiling results are not 
> useful.... A method (parsing xml) takes 150 s but without profiling , it's 
> 0.100 s

> Everything seems to work, so what could be the problem ?

> Thanks a lot for any help...