Closed Bug 1550745 Opened 5 years ago Closed 4 years ago

Remove "raptor-" prefix from Raptor test names

Categories

(Testing :: Raptor, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: igoldan, Unassigned)

References

Details

All of our Raptor tests start with the raptor- prefix.
This is redundant, because no matter their name, all of them are grouped under the same Raptor framework.

Let's drop the prefix.

+1 thanks Ionut

This is a easy fix.

:igoldan will this affect the way data is submitted to perfherder?
Will we keep the historical reference if we make this change?

Flags: needinfo?(igoldan)

(In reply to Florin Strugariu [:Bebe] (needinfo me) from comment #2)

This is a easy fix.

:igoldan will this affect the way data is submitted to perfherder?
Will we keep the historical reference if we make this change?

This will disconnect the signatures. We will retain the old data, but the
new data will appear as originating from a whole new test.

As Perf sheriffs, we'll be blind on Raptor alerts for half a day, until Perfherder
gains enough data to identify regression/improvement patterns again.

Flags: needinfo?(igoldan)

:davehunt would this be acceptable?

Flags: needinfo?(dave.hunt)

(In reply to Florin Strugariu [:Bebe] (needinfo me) from comment #4)

:davehunt would this be acceptable?

This will potentially also impact any dashboard that presents raptor test results, and any queries that people may have. Perhaps it would be better to phase out the prefix by ensuring there is no code within raptor that depends on it, allowing any new tests to omit it. For presentation in tools such as Perfherder, we could simply strip the prefix for any tests that carry it.

Flags: needinfo?(dave.hunt)
Depends on: 1583539

I believe this issue will be addressed by bug 1583539.

Priority: P2 → P3

The browsertime tests do not have the "raptor-" prefix, and we're planning to migrate all tests to browsertime.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.