Closed Bug 888369 Opened 11 years ago Closed 7 years ago

use xperf_whitelist.json from m-c in talos xperf jobs

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jmaher, Unassigned)

References

Details

Currently we pull talos.json from m-c to find the location of talos.zip.  I would like to reuse talos_from_code.py (http://mxr.mozilla.org/mozilla-central/source/testing/talos/talos_from_code.py), to pull down additional talos files.

Right now in bug 875914, we are looking to define a set of known files and access patterns.  This would be really nice to have in m-c so we can query/adjust as necessary without having to deploy a new talos.zip.  

I propose putting the file in m-c/testing/talos/xperf_whitelist.json, which would need to be downloaded to the talos directory.

Please weigh in on what I might be overlooking.
Blocks: 875914
Product: mozilla.org → Release Engineering
still needed? what are the next steps here?
Flags: needinfo?(jmaher)
actually talos is in tree now, so this is not needed anymore.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jmaher)
Resolution: --- → WONTFIX
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.