Open Bug 1583539 Opened 3 months ago Updated 24 days ago

Provide mechanism for renaming suite/test names

Categories

(Tree Management :: Perfherder, task, P3)

Tracking

(Not tracked)

People

(Reporter: igoldan, Unassigned)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

(Keywords: meta)

This is an old problem that tends to haunt us from time to time.

Suite/test names for perf tests can get very big, ugly & hard to read.
Renaming them disconnects the data points.

Warning: implementation details bellow! May turn out to be a bad track!
I think we should treat the suite/test names we already have as untouchable. Don't ever try to rename them, even if they have a typo.

Then create the concept of public suite/test names. Renaming them won't disconnect the data points. But it will reflect in all Perfherder's views, improving readability for them by a lot (where needed).

For this to work, I think a new table with a max of 4 fields like initial_suite, initial_test, public_suite_name, public_test_name would do the trick.
initial_suite & initial_test could be indexed & treated as a composite unique key, for faster joins. initial_suite & initial_test are basically foreign keys pointing to our existing suite & test names.

I like the idea of the test name having an alternative name for presentation purposes.

Thinking more about this, I don't consider we yet need a new table.
Simply providing new columns to the existing performance_signature table should do the required job.

We'll also need a web API for doing the actual updates.

Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.