Triaging Networking Bugs

  • Revision slug: Triaging_Networking_Bugs
  • Revision title: Triaging Networking Bugs
  • Revision id: 174572
  • Created:
  • Creator: Kohei
  • Is current revision? No
  • Comment Updated the page title

Revision Content

Ok, so you are interested in helping us triage networking bugs. Excellent! Here's some things you should know...

File bugs in the right component

Meet the components...

Networking          - general networking bugs go here (including DNS bugs)
Networking: Cache   - cache specific bugs
Networking: File    - file specific bugs
Networking: FTP     - ftp specific bugs
Networking: HTTP    - http and https specific bugs (including http proxy and ssl tunnel)

Use the status whiteboard tags

These tags help the developers and other triagers quickly understand what kind of bug they are looking at.

[DUPEME]            - bug is likely a duplicate (mention possible duplicate reports in comments)
[http/1.1]          - bug has to do with HTTP/1.1 spec compliance
[pipelining]        - bug only occurs when pipelining is enabled  
[proxy]             - bug has to do with proxy servers
[digest-auth]       - bug has to do with digest authentication
[ntlm-auth]         - bug has to do with NTLM authentication
[dns]               - bug has to do with DNS problems

run queries:

If the bug reports a problem in an older build, ask the reporter to try a more recent build

This is pretty obvious, but often times a bug report will sit around with comments about a problem that has been fixed already.

If the problem is not obvious, ask the reporter to capture a network log

See for example the HTTP Debugging Guide A problem can sometimes be diagnosed in a matter of seconds when there is a log available. NSRP logs as well as tcpdumps can each be extremely valuable.

Check for commonly filed bugs

When triaging be sure to keep in mind the list of most frequently duped bug reports. Check the most frequently reported bugs and the most frequently duplicated bugs.

Be careful when marking bugs as duplicates

Just because the symptoms of two bugs appear similar, it does not mean that the bugs have the same root cause. Sometimes distinct problems can share the same symptoms. For example, consider a bug report that says "Mozilla shows an empty page." There could any number of explanations for such a problem. Sometimes it requires a knowledgable developer or experienced triager to determine that too bugs are indeed caused by the same problem. Invalid duplicates cause valid bug reports to be lost, so be extra careful when you resolve a bug as a duplicate. If you are at all uncertain, it is better to simply flag the bug report with <tt>{{mediawiki.external('DUPEME')}}</tt> in the status whiteboard field and explain what the possible duplicate bug report might be.

Original Document Information

  • Author(s): Darin Fisher
  • Last Updated Date: June 16, 2004
  • Copyright Information: Portions of this content are © 1998–2007 by individual mozilla.org contributors; content available under a Creative Commons license | Details.

Revision Source

<p>Ok, so you are interested in helping us triage networking bugs.  Excellent! Here's some things you should know...
</p>
<h3 name="File_bugs_in_the_right_component"> File bugs in the right component </h3>
<p>Meet the components...
</p>
<pre>Networking          - general networking bugs go here (including DNS bugs)
Networking: Cache   - cache specific bugs
Networking: File    - file specific bugs
Networking: FTP     - ftp specific bugs
Networking: HTTP    - http and https specific bugs (including http proxy and ssl tunnel)
</pre>
<h3 name="Use_the_status_whiteboard_tags"> Use the status whiteboard tags </h3>
<p>These tags help the developers and other triagers quickly understand what kind of bug they are looking at.
</p>
<pre>[DUPEME]            - bug is likely a duplicate (mention possible duplicate reports in comments)
[http/1.1]          - bug has to do with HTTP/1.1 spec compliance
[pipelining]        - bug only occurs when pipelining is enabled  
[proxy]             - bug has to do with proxy servers
[digest-auth]       - bug has to do with digest authentication
[ntlm-auth]         - bug has to do with NTLM authentication
[dns]               - bug has to do with DNS problems
</pre>
<p>run queries:
</p>
<ul><li> <a class="external" href="http://bugzilla.mozilla.org/buglist.cgi?product=Browser&amp;component=Networking&amp;component=Networking%3A+Cache&amp;component=Networking%3A+File&amp;component=Networking%3A+FTP&amp;component=Networking%3A+HTTP&amp;status_whiteboard_type=anywordssubstr&amp;status_whiteboard=DUPEME&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">DUPEME</a>
</li><li> <a class="external" href="http://bugzilla.mozilla.org/buglist.cgi?product=Browser&amp;component=Networking&amp;component=Networking%3A+Cache&amp;component=Networking%3A+File&amp;component=Networking%3A+FTP&amp;component=Networking%3A+HTTP&amp;status_whiteboard_type=anywordssubstr&amp;status_whiteboard=http%2F1.1&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">http/1.1</a>
</li><li> <a class="external" href="http://bugzilla.mozilla.org/buglist.cgi?product=Browser&amp;component=Networking&amp;component=Networking%3A+Cache&amp;component=Networking%3A+File&amp;component=Networking%3A+FTP&amp;component=Networking%3A+HTTP&amp;status_whiteboard_type=anywordssubstr&amp;status_whiteboard=pipelining&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">pipelining</a>
</li><li> <a class="external" href="http://bugzilla.mozilla.org/buglist.cgi?product=Browser&amp;component=Networking&amp;component=Networking%3A+Cache&amp;component=Networking%3A+File&amp;component=Networking%3A+FTP&amp;component=Networking%3A+HTTP&amp;status_whiteboard_type=anywordssubstr&amp;status_whiteboard=proxy&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">proxy</a>
</li><li> <a class="external" href="http://bugzilla.mozilla.org/buglist.cgi?product=Browser&amp;component=Networking&amp;component=Networking%3A+Cache&amp;component=Networking%3A+File&amp;component=Networking%3A+FTP&amp;component=Networking%3A+HTTP&amp;status_whiteboard_type=anywordssubstr&amp;status_whiteboard=digest-auth&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">digest-auth</a>
</li><li> <a class="external" href="http://bugzilla.mozilla.org/buglist.cgi?product=Browser&amp;component=Networking&amp;component=Networking%3A+Cache&amp;component=Networking%3A+File&amp;component=Networking%3A+FTP&amp;component=Networking%3A+HTTP&amp;status_whiteboard_type=anywordssubstr&amp;status_whiteboard=ntlm-auth&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">ntlm-auth</a>
</li><li> <a class="external" href="http://bugzilla.mozilla.org/buglist.cgi?product=Browser&amp;component=Networking&amp;component=Networking%3A+Cache&amp;component=Networking%3A+File&amp;component=Networking%3A+FTP&amp;component=Networking%3A+HTTP&amp;status_whiteboard_type=anywordssubstr&amp;status_whiteboard=dns&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">dns</a>
</li></ul>
<h3 name="If_the_bug_reports_a_problem_in_an_older_build.2C_ask_the_reporter_to_try_a_more_recent_build"> If the bug reports a problem in an older build, ask the reporter to try a more recent build </h3>
<p>This is pretty obvious, but often times a bug report will sit around with comments about a problem that has been fixed already.
</p>
<h3 name="If_the_problem_is_not_obvious.2C_ask_the_reporter_to_capture_a_network_log"> If the problem is not obvious, ask the reporter to capture a network log </h3>
<p>See for example the <a href="en/HTTP_Logging">HTTP Debugging Guide</a> A problem can sometimes be diagnosed in a matter of seconds when there is a log available.  NSRP logs as well as tcpdumps can each be extremely valuable.
</p>
<h3 name="Check_for_commonly_filed_bugs"> Check for commonly filed bugs </h3>
<p>When triaging be sure to keep in mind the list of most frequently duped bug reports.  Check the <a class="external" href="https://bugzilla.mozilla.org/duplicates.html">most frequently reported bugs</a> and the <a class="external" href="http://bugzilla.mozilla.org/duplicates.cgi?sortby=bug_no">most frequently duplicated bugs</a>.
</p>
<h3 name="Be_careful_when_marking_bugs_as_duplicates"> Be careful when marking bugs as duplicates </h3>
<p>Just because the symptoms of two bugs appear similar, it does not mean that the bugs have the same root cause.  Sometimes distinct problems can share the same symptoms.  For example, consider a bug report that says "Mozilla shows an empty page."  There could any number of explanations for such a problem. Sometimes it requires a knowledgable developer or experienced triager to determine that too bugs are indeed caused by the same problem.  <u>Invalid duplicates cause valid bug reports to be lost, so be extra careful when you resolve a bug as a duplicate</u>.  If you are at all uncertain, it is better to simply flag the bug report with <tt>{{mediawiki.external('DUPEME')}}</tt> in the status whiteboard field and explain what the possible duplicate bug report might be.
</p>
<div class="originaldocinfo">
<h2 name="Original_Document_Information"> Original Document Information </h2>
<ul><li> Author(s): <a class="external" href="mailto:darin@meer.net">Darin Fisher</a>
</li><li> Last Updated Date: June 16, 2004
</li><li> Copyright Information: Portions of this content are © 1998–2007 by individual mozilla.org contributors; content available under a Creative Commons license | <a class="external" href="http://www.mozilla.org/foundation/licensing/website-content.html">Details</a>.
</li></ul>
</div>
Revert to this revision