Prune fails when OOPSes are zero in size

Bug #1270699 reported by Haw Loeung
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description


We've ran into a bug where the prune job would abort when it encounters a zero sized OOPS:

| oops_tools@neem:/srv/$ cd $OOPS_DATEDIR && bin/prune --repo /srv/ --projectgroup launchpad-project
| File: <open file '/srv/', mode 'rb' at 0xf15ec00>
| Traceback (most recent call last):
| File "bin/prune", line 26, in <module>
| oops_datedir_repo.prune.main()
| File "/srv/", line 154, in main
| repo.prune_unreferenced(prune_from, prune_until, references)
| File "/srv/", line 289, in prune_unreferenced
| report =
| File "/srv/", line 57, in read
| raise IOError("Empty OOPS Report")
| IOError: Empty OOPS Report

| -rw-r--r-- 1 oops_tools oops_tools 0 Dec 1 22:33
| /srv/

I think what should happen is that it should skip or remove these OOPSes and continue pruning the rest.



Haw Loeung (hloeung)
tags: added: canonical-webops-oops
Ioana Lasc (ilasc)
Changed in python-oops-tools:
importance: Undecided → High
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.