On Thu, 10 Apr 2003, Bryn Reeves wrote:
> I'm getting a few of these errors for runs which have partially
> failed. Sometimes (around 50% of the time) if I kill the polyclt
> process with ctrl-c because something has gone wrong, I am unable to
> extract any phase stats from the file, even using --phases for
> phases which are known to have completed.
>
> The only information I can get from these files is the console log
> via lr.
>
> Anyone have any suggestions on how I could possibly recover some of
> the data from these?
If you are using 2.7.6 on FreeBSD, then most likely, you kill polyclt
when it is too late -- the process was not allowed or could not flush
phase stats (e.g., it ran out of memory). If you are running on
another OS, there might be some unknown compatibility problem.
Why don't you e-mail me the console (if you have it) and binary logs,
compressed, privately, and we will go from there.
> The reason that I want to do this is that while testing development
> units, sometimes the test will fail at a certain point for a known
> reason but the preceding phases should still carry useful info for
> us.
Yes, it is a common reason and the trick "should work".
Thanks,
Alex.
--
| HTTP performance - Web Polygraph benchmark
www.measurement-factory.com | HTTP compliance+ - Co-Advisor test suite
| all of the above - PolyBox appliance
This archive was generated by hypermail 2b29 : Mon Feb 06 2006 - 12:00:26 MST