** Changed in: pybootchartgui (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: pybootchartgui (Ubuntu)
Status: Confirmed => New
** Changed in: pybootchartgui (Ubuntu)
Status: New => Fix Released
--
pybootchartgui crashed with ZeroDivisionError in draw_chart()
https
Ubuntu updated to -r139
** Changed in: pybootchartgui (Ubuntu)
Status: New => Fix Released
--
pybootchartgui crashed with ZeroDivisionError in draw_chart()
https://bugs.launchpad.net/bugs/441660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Hmm, since the divisor is the maximum of the timeseries of {CPU-use, I/O
wait, disk-throughput, disk utilization}, and neither of those series
should be all zeroes, I don't think there is any possibility of divide-
by-zero for properly parsed data.
--
pybootchartgui crashed with ZeroDivisionError
One other thought: some kind of fix for potential division-by-zero
errors should probably still be added. I didn't look closely at the
meaning of the data, but if very short time intervals have the potential
to be zero (depending on the time granularity available), this could
still be a problem on
Anders,
Thanks for looking at this and thanks for the fix! I should have looked
closer at the bootchart data. ;)
Yeah, the Linux virtio para-virtual block devices are /dev/vd{a,b,c,...}
Cheers,
Jason
--
pybootchartgui crashed with ZeroDivisionError in draw_chart()
https://bugs.launchpad.net/b
Hi again,
The parsing was wrong - missing the virtual disks. This should now be
fixed in r139
http://code.google.com/p/pybootchartgui/source/detail?r=139
"Make sure parsing also matches virtual disks, conventionally called vda, vdb
etc. - should fix https://bugs.launchpad.net/bugs/441660";
Best
Hi Jason,
It looks like the disk use and disk throughput is all zeroes. I wonder
if the parsing code in pybootchartgui is broken or if somehow the
dumping of diskusage data is broken when running in QEMU.
I'll look a bit more and run bootchart in some VM's.
Otherwise maybe just doing
ys
I attached the most recent bootchart data I was testing on, but I've
personally encountered this bug consistently for about the last month
during I've been testing Karmic in a VM.
I also revised my fix, please see revno 5 in
lp:~jderose/ubuntu/karmic/pybootchartgui/fix-441660 (it now shows up in
t
If you upload the datafile /var/log/bootchart/username-desktop-
karmic-20091003-2.tgz then I'll have a look too.
Best
Anders (upstream)
--
pybootchartgui crashed with ZeroDivisionError in draw_chart()
https://bugs.launchpad.net/bugs/441660
You received this bug notification because you are a mem
I have a fix in lp:~jderose/ubuntu/karmic/pybootchartgui/fix-441660 and
proposed a merge into lp:ubuntu/pybootchartgui
--
pybootchartgui crashed with ZeroDivisionError in draw_chart()
https://bugs.launchpad.net/bugs/441660
You received this bug notification because you are a member of Ubuntu
Bugs
** Branch linked: lp:~jderose/ubuntu/karmic/pybootchartgui/fix-441660
--
pybootchartgui crashed with ZeroDivisionError in draw_chart()
https://bugs.launchpad.net/bugs/441660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Visibility changed to: Public
--
pybootchartgui crashed with ZeroDivisionError in draw_chart()
https://bugs.launchpad.net/bugs/441660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
12 matches
Mail list logo
