Rename "twinopen ext+twinopen:twinopen.html" to "twinopen"
Categories
(Testing :: Talos, task, P3)
Tracking
(Not tracked)
People
(Reporter: bdahl, Unassigned)
Details
On perfherder the twinopen test shows up as "twinopen ext+twinopen:twinopen.html" which I find to be a confusing name as it's not really a pageloader test. Can we get it to just display as "twinopen".
|
||
Comment 1•6 years ago
|
||
:davehunt, this is a new test that was added last month to Talos, it needs a renaming- I know :igoldan has done some related work, this would need to fix the name output from talos as well as fixing the database in perfherder. Could you help :bdahl out here.
|
||
Updated•6 years ago
|
|
||
Comment 2•6 years ago
|
||
Is it necessary to rename the data associated with the test if it's new? We have renamed in a couple of cases, but doing so is time consuming. Can we just rename the test name sent to Perfherder?
|
|
||
Updated•6 years ago
|
|
Reporter | |
Comment 3•6 years ago
|
||
If it's a pain let's just leave as is. I updated the name on the wiki page.
|
|
||
Comment 4•6 years ago
|
||
(In reply to Brendan Dahl [:bdahl] from comment #3)
If it's a pain let's just leave as is. I updated the name on the wiki page.
I'm in favour of changing the test name, I just wanted to know if renaming the historic data is a requirement here, or can we just use the new name going forward?
|
|
Reporter | |
Comment 5•6 years ago
|
||
Do we need much historical data to catch regressions? If not, I'm fine with just renaming going forward.
|
|
||
Comment 6•6 years ago
|
||
(In reply to Brendan Dahl [:bdahl] from comment #5)
Do we need much historical data to catch regressions? If not, I'm fine with just renaming going forward.
There would be a brief period where our sheriffs would need to manually observe any regressions, however this wouldn't be avoided by performing a deeper rename as the time taken to perform the rename will exceed the window we would need to observe.
Description
•