Add the tracing unittests to the Chromium CQ |
||||
Issue descriptionWe're run into issues updating our Canary reference builds because of tests failing when we switch to the newer Chromium version. We should add the tracing unittests to the chromium CQ to catch Chromium changes that would break the traceviewer.
,
Oct 6 2016
This just happens again: https://github.com/catapult-project/catapult/issues/2907
,
Oct 6 2016
Sorry for jumping to conclusion too quickly, all the trace viewer test passed in my TOT chrome build, so even with this fixed, https://github.com/catapult-project/catapult/issues/2907 will still happen.
,
Feb 2 2017
,
Jan 29 2018
This is good to have. Not sure who should own this bug now, marking it to 'available' s.t anyone in the team can pick it up.
,
Nov 12
|
||||
►
Sign in to add a comment |
||||
Comment 1 by martiniss@chromium.org
, Sep 26 2016Components: -Infra Infra>Client>Chrome