bzr branch import script oopses sometimes

Bug #438039 reported by Henning Eggers on 2009-09-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Henning Eggers

Bug Description

Have an example:

Oops-Id: OOPS-1366RSBR1
Exception-Type: NoSuchFile
Exception-Value: No such file: ('TREE_ROOT', 'michael@laptop-20090927090009-nl41nfl4puh8q52l')
Date: 2009-09-27T10:10:23.234080+00:00
Branch: None
Revision: None
User: None
URL: None
Duration: -1

branch_job_type=Rosetta Upload

Traceback (most recent call last):
  Module, line 140, in runAll
  Module, line 121, in runJob
  Module lp.code.model.branchjob, line 791, in run
  Module lp.code.model.branchjob, line 761, in _init_translation_file_lists
  Module bzrlib.revisiontree, line 68, in get_file_text
    _, content = list(self.iter_files_bytes([(file_id, None)]))[0]
  Module bzrlib.revisiontree, line 84, in iter_files_bytes
    raise errors.NoSuchFile(e.revision_id)
NoSuchFile: No such file: ('TREE_ROOT', 'michael@laptop-20090927090009-nl41nfl4puh8q52l')

Related branches

Henning Eggers (henninge) wrote :

If a branch is affected by this, there is no way to have its translation files uploaded. So users that are struck by this cannot get their translations into rosetta.

It seems that only those branches are affected where bzlib considers the root of the tree to be changed. This are most likely new branches.

Changed in rosetta:
importance: High → Critical
Henning Eggers (henninge) wrote :

These OOPSES have only been occuring since the 3.0 roll-out but before the re-roll on 25 Sep. This means they were not obscured by the fix in the job runner as mentioned in bug 434192.

Henning Eggers (henninge) wrote :

I mean, they were not obscured by the *bug* that was fixed .... ;-)

Henning Eggers (henninge) wrote :

There was a fix but I guess that is not the end of the story ... I still see OOPses ... :-(

Changed in rosetta:
status: In Progress → Fix Released
status: Fix Released → In Progress
Michael Barnett (mbarnett) wrote :

I have updated the correct production branch with your changes. Hopefully NOW the OOPses will cease.

Michael Barnett (mbarnett) wrote :

per my email my changes were unsuccessful and i have reverted them. I'll get this working first thing monday.

Henning Eggers (henninge) wrote :

No OOPSes related to this error since 2009-10-04 when the patch was applied succesfully. Thanks Michael!

Changed in rosetta:
status: In Progress → Fix Released
Ursula Junque (ursinha) on 2009-10-22
tags: added: qa-needstesting
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers