Should mark imports as invalid on some exceptions

Bug #616812 reported by Jelmer Vernooij
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Jelmer Vernooij

Bug Description

  affects launchpad-code

bzr-svn/bzr-git/bzr-hg will raise reasonable exceptions on errors that
are not bugs. To make it easier to find the actual problematic imports
and not having to do manual import gardening, it would be nice if the
importds could catch those exceptions and automatically mark the import
as invalid rather than failing; perhaps also update the whiteboard?

The exception classes I think would be good candidates for marking an
import as invalid are:

 * bzrlib.errors.NoRepositoryPresent
 * bzrlib.errors.NotBranchError
 * repeated bzrlib.errors.ConnectionError (host not found, etc)

Candidates for automatic suspension:

 * bzrlib.plugins.svn.errors.InvalidFileName
 * bzrlib.plugins.git.fetch.SubmodulesRequireSubtrees

Related branches

Tim Penhey (thumper)
tags: added: code-import
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Low
Jelmer Vernooij (jelmer)
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Jelmer Vernooij (jelmer)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Jelmer Vernooij (jelmer)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
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.