fix how ts/tp style tests are identified by talos

RESOLVED FIXED

Status

P2
normal
RESOLVED FIXED
9 years ago
5 years ago

People

(Reporter: anodelman, Assigned: anodelman)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

9 years ago
Talos currently determines what format test results are in by looking through a list of ts-style tests.  If the test name is not in the list then it assumes that the test format is tp-style.  This means having to maintain a list of ts-style tests, which makes adding new tests a headache.

Should be able to handle this programatically.
(Assignee)

Updated

9 years ago
Blocks: 515490
(Assignee)

Updated

9 years ago
Assignee: nobody → anodelman
Priority: -- → P2
(Assignee)

Comment 1

9 years ago
Created attachment 400911 [details] [diff] [review]
set results format based upon communication with the browser

No more maintenance of a giant list of tests.
Attachment #400911 - Flags: review?(catlee)
(Assignee)

Comment 2

9 years ago
Created attachment 401093 [details] [diff] [review]
set results format based upon communication with the browser (take 2)
Attachment #400911 - Attachment is obsolete: true
Attachment #401093 - Flags: review?(catlee)
Attachment #400911 - Flags: review?(catlee)

Updated

9 years ago
Attachment #401093 - Flags: review?(catlee) → review+
Comment on attachment 401093 [details] [diff] [review]
set results format based upon communication with the browser (take 2)

Checking in run_tests.py;
/cvsroot/mozilla/testing/performance/talos/run_tests.py,v  <--  run_tests.py
new revision: 1.52; previous revision: 1.51
done
Checking in ttest.py;
/cvsroot/mozilla/testing/performance/talos/ttest.py,v  <--  ttest.py
new revision: 1.32; previous revision: 1.31
done
Attachment #401093 - Flags: checked-in+
(Assignee)

Comment 4

9 years ago
Landed and working.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.