Closed
Bug 1090421
Opened 10 years ago
Closed 10 years ago
e10s suitenames need to be adjusted for holly
Categories
(Testing :: Talos, defect)
Tracking
(e10s+)
RESOLVED
FIXED
mozilla36
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: wlach, Assigned: jmaher)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
7.14 KB,
patch
|
wlach
:
review+
|
Details | Diff | Splinter Review |
Talos "other" seems to be failing on holly because of an undefined suitename: https://treeherder.mozilla.org/ui/#/jobs?repo=holly&revision=252f6ee39d3e Seeing weird errors like this: Badly formed talos_json for suite other-e10s_l64; KeyError trying to access talos_config['suites'][other-e10s_l64]['tests']: 'other-e10s_l64' No tests specified; please specify --tests Running post_fatal callback... Exiting -1 I think fixing this is likely just a matter of adjusting the suite names in talos.json and/or adjusting the mozharness arguments of what should be run.
Assignee | ||
Comment 1•10 years ago
|
||
ok, we are missing the talos.json definitions: https://hg.mozilla.org/projects/holly/file/tip/testing/talos/talos.json buildbotconfigs have proper settings, but we have defined in talos.json "other-e10s" and we need to define "other-e10s_nol64" and "other-e10s_l64". That should solve the bulk of these problems. Here is the list of tests jobs we have defined in buildbotconfigs: ('chromez-e10s', 'dromaeojs-e10s', 'g1-e10s', 'other-e10s_l64', 'other-e10s_nol64', 'tp5o-e10s', 'svgr-e10s', 'xperf-e10s') The talos.json on inbound doesn't have e10s changes? should we add those in, or just fix this on holly?
Flags: needinfo?(wmccloskey)
Updated•10 years ago
|
Blocks: e10s-harness
tracking-e10s:
--- → +
I'm afraid I don't understand this stuff. It would be great to get as much as possible checked into inbound though. We want the diff between inbound and holly to be as small as possible.
Flags: needinfo?(wmccloskey)
Reporter | ||
Comment 3•10 years ago
|
||
(In reply to Bill McCloskey (:billm) from comment #2) > I'm afraid I don't understand this stuff. It would be great to get as much > as possible checked into inbound though. We want the diff between inbound > and holly to be as small as possible. Yeah, jmaher and I basically agreed to check-in a fixed version of the holly talos.json to m-c. The e10s suites don't do any harm there (they just aren't run).
Assignee | ||
Comment 4•10 years ago
|
||
Attachment #8513448 -
Flags: review?(wlachance)
Reporter | ||
Comment 5•10 years ago
|
||
Comment on attachment 8513448 [details] [diff] [review] update talos.json on inbound with e10s definitions (1.0) Review of attachment 8513448 [details] [diff] [review]: ----------------------------------------------------------------- lgtm
Attachment #8513448 -
Flags: review?(wlachance) → review+
Assignee | ||
Comment 6•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/24241717af63
Comment 7•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/24241717af63
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
You need to log in
before you can comment on or make changes to this bug.
Description
•