New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 649753 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Add the tracing unittests to the Chromium CQ

Project Member Reported by aiolos@chromium.org, Sep 23 2016

Issue description

We'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.
 
Cc: benhenry@chromium.org
Components: -Infra Infra>Client>Chrome
Adding a test to the CQ is generally an involved process. You need to get permission from chrome-eng-review, and you need proof that your test won't add that much to the overall CQ cycle time.

If you want to get this process started, you should follow the instructions at https://chromium.googlesource.com/chromium/tools/build.git/+/master/scripts/slave/recipe_modules/chromium_tests/chromium_recipe.md#Create-a-New-Trybot, under the section "Getting your trybot on the CQ".... which says to email chrome-infra. So go ahead and do that.
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.
Components: Speed>Tracing
Labels: -Performance-Tracing
Status: Available (was: Untriaged)
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.
Cc: -eakuefner@chromium.org

Sign in to add a comment