Re: amreport taper stats bug in 3.3.2

2012-10-19 Thread Jean-Louis Martineau
On 10/19/2012 01:12 PM, Jean-Francois Malouin wrote: * Jean-Louis Martineau [20121019 12:39]: Jean-Francois, I already committed many fixes that should improve it a lot. There are still some case where it will report too much time (waiting for the driver or operating the changers), they are on

Re: amreport taper stats bug in 3.3.2

2012-10-19 Thread Jean-Francois Malouin
* Jean-Louis Martineau [20121019 12:39]: > Jean-Francois, > > I already committed many fixes that should improve it a lot. > There are still some case where it will report too much time > (waiting for the driver or operating the changers), they are on my > list of things to fix, but as they are o

Re: amreport taper stats bug in 3.3.2

2012-10-19 Thread Jean-Louis Martineau
Jean-Francois, I already committed many fixes that should improve it a lot. There are still some case where it will report too much time (waiting for the driver or operating the changers), they are on my list of things to fix, but as they are only cosmetic, they do not get a high priority. Je

Re: amreport taper stats bug in 3.3.2

2012-10-18 Thread Jean-Francois Malouin
No takers on this one? jf * Jean-Francois Malouin [20121005 15:11]: > Hi, > > Just upgraded to 3.3.2 from 3.3.0 and I noticed the same problem that > I reported back in summer 2010 when I upgraded to 3.1.1: amreport > taper stats are not indicative of the real tape performance when > flushing

amreport taper stats bug in 3.3.2

2012-10-05 Thread Jean-Francois Malouin
Hi, Just upgraded to 3.3.2 from 3.3.0 and I noticed the same problem that I reported back in summer 2010 when I upgraded to 3.1.1: amreport taper stats are not indicative of the real tape performance when flushing parameters are in effect. 3.3.0 didn't have this problem btw. I'm using the flushi