could use python-oops to record errors

Bug #827074 reported by Martin Pool
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Distributed Development
Triaged
Medium
Unassigned

Bug Description

It might be useful if the udd importer unified its error tracking code with https://launchpad.net/python-oops; that would be a good foundation for capturing more information (like local variables or a timeline.)

12:40
lifeless: poolie: you should be able to configure and publish an oops from that system now, with lp:python-oops and lp:python-oops-datedir-repo
lifeless: config = oops.Config()
lifeless: repo = oops_datedir_repo.DateDirRepo('/where/the/oopses/go', 'packageimporter')
poolie: nice
lifeless: report = config.create()
lifeless: # flesh it out
lifeless: config.publish(report)
lifeless: # bah I forgot a step -
lifeless: config.publishers.append(repo.publish)

Revision history for this message
Robert Collins (lifeless) wrote :

For a time line -
activities = timeline.timeline.Timeline()
action = activities.start('checkout', 'ubuntu:gcc')
...
action.finish()

etc, then if an oops occurs you can suck the data out of the timeline.

Revision history for this message
Jonathan Lange (jml) wrote :

Now that we're using this for pkgme and have the awesome new oops service, we'd really like this.

Changed in udd:
status: Confirmed → Triaged
Tom Haddon (mthaddon)
tags: added: canonical-losa-ca
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.