Chrome Network Bug Triage

The Chrome network team uses a two day bug triage rotation. The goal is to review outstanding issues and keep things moving forward. The rotation is time based rather than objective based. Sheriffs are expected to spend the majority of their two days working on bug triage/investigation.

1. Review untriaged bugs

Look through this list of untriaged bugs.

  • Go through them in the given order (top to bottom). The link sorts them by priority and then recency.
  • The goal is to move them out of the untriaged bug queue and give them a priority.

For each bug try to:

  • Remove the Internals>Network component if it belongs elsewhere
  • Dupe it against an existing bug
  • Close it WontFix if appropriate
  • Give the bug a priority. Refer to this (internal) document for guidelines
  • If the bug is a potential security issue (Allows for code execution from remote site, allows crossing security boundaries, unchecked array bounds, etc) mark it Type-Bug-Security.
  • If the bug has privacy implications mark it with component Privacy.
  • Mark it as a feature request or task if appropriate
  • Ask the reporter to narrow down regressions, possibly by using bisect-builds-py. To view suspicious changelists in a regression window, you can use the Change Log form on OmahaProxy
  • CC others who may be able to help
  • Mark it as Needs-Feedback and request more information if needed.
  • In cases where the bug has multiple components, but primary ownership falls outside of networking, further network triage may not be possible. In those cases, if possible remove the networking component. Otherwise, add the Network-Triaged label to the bug, and add a comment explaining which team should triage further. Adding the Network-Triaged serves to filter the bug from our untriaged bug list.
  • Request a NetLog that captures the problem. You can paste this on the bug:
    Please collect and attach a chrome://net-export log.
    Instructions can be found here:
  • If a NetLog was provided, try to spend a bit of time reviewing it. See for an introduction.
  • Move to a subcomponent of Internals>Network if appropriate. See for an overview of the components.
  • If the bug is a crash, see internal: Dealing with a crash ID and internal: Investigating crashers

2. Follow-up on issues with the Needs-Feedback label

Look through this list of Needs=Feedback bugs.

  • Go through them in the given order (top to bottom). The link sorts them by priority and then recency.
  • If the requested feedback was provided, review the new information and repeat the same steps as (1) to re-triage based on the new information.
  • If the bug had the Needs-Feedback label for over a week and the feedback needed to make progress was not yet provided, archive the bug.

3. (Optional) Look through crash reports

Top crashes will already be entered into the bug system by a different process, so will be handled by the triage steps above.

However if you have time to look through lower threshold crashes, see internal: Looking for new crashers

4. Send out a sheriff report

On the final day of your rotation, send a brief summary to detailing any interesting or concerning trends. Do not discuss any restricted bugs on the public mailing list.