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

Issue 921123 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jan 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 921122



Sign in to add a comment

Merge Tests>Telemetry and Speed>Telemetry

Project Member Reported by crouleau@chromium.org, Jan 11

Issue description

Ned, Emily, Juan,

Could you please let me know if there is any reason to have both of these? Otherwise please respond with LGTM. If there is not, then I will find an admin who can merge them.

(Sorry Ned, I know you're trying to get off of these Telemetry bugs, but you have the most history here. You can drop yourself from the CC list after you let me know whether we still need both for any reason.)

Also, I don't really care whether we keep Tests>Telemetry or Speed>Telemetry in the end, but I'll put out as the straw man that we keep "Tests>Telemetry" (or "Test>Telemetry" if that is where we are going.)

 
Description: Show this description
Test>Telemetry is supposed for correctness testing stuffs, e.g: gpu tests. These are bugs related to the browser startup reliablity, how to simulate certain user interactions, the correctness harness

Speed>Telemetry is for benchmarking/perf aspect. Example are bugs about whether we should collect garbage on the browser between story run in the benchmark loop.


For that reason, we keep two separate bug component. Though with the new Chrome iniative of 1 team = 1 bug component, I support the decision to merge the two. Maybe we just need different bug labels to distinguish between the correctness testing & perf aspect of Telemetry
Thanks for the information, Ned!

I think that since the rather small CCA is owning both functional and perf testing sides of Telemetry, it's fine to have just one component. The other thing is that if the component system isn't obvious to all the team members then people just won't follow it anyways, so I prefer a simple solution.

Emily, Juan, please respond with LGTM unless you have some concern, and I will move forward.
Merge LGTM.
lgtm
Owner: benhenry@chromium.org
Hi Ben,

Do you think you could please move all the bugs that are currently in Tests>Telemetry and Speed>Telemetry into a new "Test>Telemetry" component?

Note that we still have a Speed>Benchmarks component, but I guess we will leave that alone for now.
Cc: -nedngu...@google.com

Comment 8 by benhenry@google.com, Jan 16 (6 days ago)

Components: Test>Telemetry

Comment 9 by benhenry@google.com, Jan 16 (6 days ago)

Components: -Tests>Telemetry

Comment 10 by benhenry@google.com, Jan 16 (6 days ago)

Status: Fixed (was: Assigned)
There are >3600 issues in Tests>Telemetry, so I'm only moving the 340 open issues. I've deprecated Tests>Telemetry.

For Speed>Telemetry, I've moved all issues to Test>Telemetry and can delete the component.

Also - LOL on the fact that I had to refresh this because of my changes.

Comment 11 by crouleau@chromium.org, Jan 16 (6 days ago)

Thanks Ben!

Sign in to add a comment