Closed
Bug 1472680
Opened 6 years ago
Closed 2 years ago
Rename ClassifiedFailure and FailureClassification
Categories
(Tree Management :: Treeherder, enhancement, P3)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ghickman, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
These two models/tables cover different concepts in our data model but their names are confusingly similar.
FailureClassification is effectively an ENUM of failure types (intermittent, infra, etc). It's used to define the type of failure for a Job (& JobNote).
ClassifiedFailure models a test failure, which can occur in one or more log lines.
This bug is to decide on how we rename and how in-depth that renaming is.
My suggestion for naming:
* FailureClassification -> FailureType
* ClassifiedFailure -> Classification
I feel this matches their usage in the data model and the nomenclature we use throughout the app.
and for how deep we go:
Rename the database tables on the basis that it's not an expensive migration. This will reduce confusion for anyone else trying to understand the schema but I don't think it's necessarily worth closing the trees for.
Suggestons and comments appreciated!
Reporter | ||
Updated•6 years ago
|
Assignee: nobody → ghickman
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Assignee: ghickman → nobody
Updated•6 years ago
|
Priority: -- → P3
Comment 2•2 years ago
|
||
cleaning up old bugs
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•