OLD | NEW |
1 # Chrome Network Bug Triage : Suggested Workflow | 1 # Chrome Network Bug Triage : Suggested Workflow |
2 | 2 |
3 [TOC] | 3 [TOC] |
4 | 4 |
5 ## Identifying unlabeled network bugs on the tracker | 5 ## Identifying unlabeled network bugs on the tracker |
6 | 6 |
7 * Look at new unconfirmed bugs since noon PST on the last triager's rotation. | 7 * Look at new unconfirmed bugs since noon PST on the last triager's rotation. |
8 [Use this issue tracker | 8 [Use this issue tracker |
9 query](https://bugs.chromium.org/p/chromium/issues/list?q=status%3Aunconfirmed
&sort=-id&num=1000). | 9 query](https://bugs.chromium.org/p/chromium/issues/list?q=status%3Aunconfirmed
&sort=-id&num=1000). |
10 | 10 |
(...skipping 72 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
83 tagged as Internals>Network. | 83 tagged as Internals>Network. |
84 | 84 |
85 * If it's not, attach appropriate labels/components and go no further. | 85 * If it's not, attach appropriate labels/components and go no further. |
86 | 86 |
87 * If it may be a network bug, attach additional possibly relevant component if | 87 * If it may be a network bug, attach additional possibly relevant component if |
88 any, and continue investigating. Once you either determine it's a | 88 any, and continue investigating. Once you either determine it's a |
89 non-network bug, or figure out accurate more specific network components, your | 89 non-network bug, or figure out accurate more specific network components, your |
90 job is done, though you should still ask for a net-internals dump if it seems | 90 job is done, though you should still ask for a net-internals dump if it seems |
91 likely to be useful. | 91 likely to be useful. |
92 | 92 |
93 * Note that ChromeOS-specific network-related code (Captive portal detection, | 93 * Note that Chrome-OS-specific network-related code (Captive portal detection, |
94 connectivity detection, login, etc) may not all have appropriate more | 94 connectivity detection, login, etc) may not all have appropriate more |
95 specific subcomponents, but are not in areas handled by the network stack | 95 specific subcomponents, but are not in areas handled by the network stack |
96 team. Just make sure those have the OS-Chrome label, and any more specific | 96 team. Just make sure those have the OS-Chrome label, and any more specific |
97 labels if applicable, and then move on. | 97 labels if applicable, and then move on. |
98 | 98 |
99 * Gather data and investigate. | 99 * Gather data and investigate. |
100 * Remember to add the Needs-Feedback label whenever waiting for the user to | 100 * Remember to add the Needs-Feedback label whenever waiting for the user to |
101 respond with more information, and remove it when not waiting on the | 101 respond with more information, and remove it when not waiting on the |
102 user. | 102 user. |
103 * Try to reproduce locally. If you can, and it's a regression, use | 103 * Try to reproduce locally. If you can, and it's a regression, use |
(...skipping 98 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
202 a crash report, and seeing if there are multiple reports for the same crash. | 202 a crash report, and seeing if there are multiple reports for the same crash. |
203 If this is the case, it may be also be malware, or an issue with an unusual | 203 If this is the case, it may be also be malware, or an issue with an unusual |
204 system/chrome/network config. | 204 system/chrome/network config. |
205 | 205 |
206 * Dig through crash reports to figure out when the crash first appeared, and | 206 * Dig through crash reports to figure out when the crash first appeared, and |
207 dig through revision history in related files to try and locate a suspect CL. | 207 dig through revision history in related files to try and locate a suspect CL. |
208 TODO(mmenke): Add more detail here. | 208 TODO(mmenke): Add more detail here. |
209 | 209 |
210 * Load crash dumps, try to figure out a cause. See | 210 * Load crash dumps, try to figure out a cause. See |
211 http://www.chromium.org/developers/crash-reports for more information | 211 http://www.chromium.org/developers/crash-reports for more information |
OLD | NEW |