Open
Bug 1107562
Opened 10 years ago
Updated 2 years ago
[Backend] Alert Manager - add support for e10s to alert manager
Categories
(Testing :: General, defect)
Testing
General
Tracking
(e10s+)
NEW
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: jmaher, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [good next bug][lang=python])
right now we run our talos tests on regular builds, but for pgo,we run both regular talos and e10s talos tests. What differentiates the e10s tests is a few things: 1) buildername: Windows 8 64-bit mozilla-central pgo talos dromaeojs-e10s <- notice the "-e10s" at the end of the test job here 2) platform has (e10s) on the end of the name as seen here: http://graphs.mozilla.org/graph.html#tests=%5B%5B255,1,49%5D%5D&sel=none&displayrange=7&datatype=running 3) platform name on the alerts has "(e10s)" as well. An example is here: https://groups.google.com/forum/#!forum/mozilla.dev.tree-management this example looks like this: "<Regression> Firefox - tscroll-ASAP - Ubuntu HW 12.04 (e10s) - 3.49%" So parse_news.py needs to parse this subject line properly and generate alerts such that we can: * identify the platform as the proper one * managed_settings.py should have support for test jobs with e10s and platforms with e10s (not sure of the most straightforward route here) * generated links to tbpl and graph server need proper names/ids
Reporter | ||
Updated•10 years ago
|
Summary: [Backout] Alert Manager - add support for e10s to alert manager → [Backend] Alert Manager - add support for e10s to alert manager
Updated•10 years ago
|
tracking-e10s:
--- → +
Updated•8 years ago
|
Blocks: e10s-tests
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•