chromeos trybot for catapult changes |
||||
Issue descriptionWe have FYI bots that run catapult and perf unittests on TOT chromeos with TOT chrome: https://uberchromegw.corp.google.com/i/chromiumos.chromium/builders/x86-generic-telemetry https://uberchromegw.corp.google.com/i/chromiumos.chromium/builders/amd64-generic-telemetry We should have similar trybots that can try a catapult change. Currently, these trybots take about 3 hours, so they are unsuitable for the catapult CQ, but we can at least run high-risk changes against these try servers as necessary.
,
Jun 29 2016
,
Jun 29 2016
From the catapult side, here's what would need to get done: build repo: Add the testers to the master, setting platform property: https://cs.chromium.org/chromium/build/masters/master.tryserver.client.catapult/builders.pyl (example cl for android: https://codereview.chromium.org/2053863002) catapult repo: Add/enable only the steps you want for CrOS in build_steps.py: https://github.com/catapult-project/catapult/blob/master/catapult_build/build_steps.py
,
Jan 16
,
Jan 16
|
||||
►
Sign in to add a comment |
||||
Comment 1 by achuith@chromium.org
, Jun 29 2016