please allow setting of a severity

Bug #749563 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Svammel (UNMAINTAINED)
Fix Released
High
Unassigned

Bug Description

please allow setting of a severity

Related branches

Revision history for this message
Mattias Backman (mabac) wrote :

If you'd like to specify one severity (which means bug task Importance I guess) that applies to all filed bugs it's an easy fix. The valid options would be.

One of:

    * Unknown
    * Critical
    * High
    * Medium
    * Low
    * Wishlist
    * Undecided

Is this what you mean?

Thanks,

Mattias

Revision history for this message
Matthias Klose (doko) wrote :

maybe my use cases are untypical ...

the same way I add a specific tag as the result of grepping the build log, I could set a severity (a test rebuild with GCC-4.6 resulting in errors that need to be fixed, and some which should be fixed (like specific compiler warnings). But again, maybe a separate tool like scanning bug reports for a tag and then re-setting the severity would do the same stuff.

Revision history for this message
Steve Langasek (vorlon) wrote :

+1 to this request. Before Matthias did his bug filing run for the x86 archive rebuild, in fact, I was poking my local branch to automatically set all bug reports to 'high' at time of filing. We can typically generalize about the severity of build failures originating from a particular archive; for a plain archive rebuild we would probably want to do 'high', for test rebuilds against a new toolchain we might do 'low', etc.

Revision history for this message
James Westby (james-w) wrote :

Let's start with an importance option that sets it for all bugs.

We can look at a per-bug importance later. That may also want to be a separate tool (because it is primarily about scanning logs rather than failures).

Thanks,

James

Changed in svammel:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Mattias Backman (mabac) wrote :

If it would happen that setting Importance fails, should the script abort or just happily continue and let the bugs have no Importance set? It's the same reflection that Steve posted in Bug #749561.

Revision history for this message
Matthias Klose (doko) wrote :

hmm, maybe fail, and continue when given an -i/--ignore-errors option?

Revision history for this message
Mattias Backman (mabac) wrote :

Hi,

I've linked to a branch that adds this feature. If it's to your liking, I'll merge it into the feature branches that are waiting to land. Trunk is still missing some important pieces, so you'll have no use for it there.

Thanks,

Mattias

Mattias Backman (mabac)
Changed in svammel:
status: Triaged → Fix Committed
Mattias Backman (mabac)
Changed in svammel:
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.