no report/log of successful packages
Bug #831699 reported by
Martin Pool
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Distributed Development |
Confirmed
|
High
|
Unassigned |
Bug Description
It would be useful if the udd importer status page and logs also showed packages that have reported successfully, as well as those that failed.
See also bug 752078.
Changed in udd: | |
assignee: | Martin Pool (mbp) → Vincent Ladeuil (vila) |
Changed in udd: | |
assignee: | Vincent Ladeuil (vila) → nobody |
Changed in udd: | |
status: | In Progress → Confirmed |
To post a comment you must log in.
There's not, at the moment, any obvious table of "successful import", in the way there is one for failures, so we could possibly infer this from other tables, or perhaps just add it as a new table. When the job succeeds (in `finish_job`) we delete the job and the failure record, and we don't obviously create anything else.
So I think we should either add a 'success' table, or refactor the current `failure` into being something like an `outcomes` record that could be either success or failure.
Also, in there, this code seems strange:
def finish_job(self, package, job_id, success, output): datetime. utcnow( ) self.JOBS_ TABLE_SELECT_ JOB,
(job_ id,)).fetchone( )
c. execute( self.JOBS_ TABLE_UPDATE,
(row[1] , 0, row[3], row[4], row[5], now, row[0])) self.FAILURES_ TABLE_FIND, (package, )).fetchone( )
c. execute( 'delete from %s where package=?'
% self.JOBS_TABLE, (package,))
c.execute( self.FAILURES_ TABLE_DELETE, (package,))
c.execute( self.OLD_ FAILURES_ TABLE_DELETE, (package,))
self. _set_failure( c, package, output, now)
self. conn.commit( )
c = self.conn.cursor()
try:
now = datetime.
if job_id > 0:
row = c.execute(
if row is not None:
if success:
row = c.execute(
if row is not None:
else:
I wonder what the logic is behind deleting the job if there was previously a failure record.