Changes between Version 3 and Version 4 of TriagingTestFailures


Ignore:
Timestamp:
Nov 2, 2010 9:32:41 AM (10 years ago)
Author:
Adam Roben
Comment:

Address some of John Sullivan's feedback

Legend:

Unmodified
Added
Removed
Modified
  • TriagingTestFailures

    v3 v4  
    4747     * No: there might be some existing platform-specific code that is responsible for the different results.
    4848
    49 = Group failures by "root cause" =
     49= File bugs for the failures =
    5050
    51 If a multiple tests are all failing for the same reason, they should be grouped together into a single root cause.
    52 
    53 = File one or more bugs for each root cause =
    54 
    55 If a test fails on multiple platforms and those platforms will need separate fixes, you should file one bug for each failing platform.
     51If multiple tests are failing for the same reason, you should group them together into a single bug. If a test fails on multiple platforms and those platforms will need separate fixes, you should file one bug for each failing platform.
    5652
    5753 1. Go to http://webkit.org/new-bug
    5854 1. Include in your report:
    5955   * The name(s) of the failing test(s)
    60    * The root cause you determined, if any
     56   * The reason you determined for the failure, if any
    6157   * What platform(s) the failures occur on
    6258   * When the failures began, if known
    6359   * A link to the failing output
    64      * If a single test had incorrect output, link to the pretty diff.
    65      * If multiple tests had incorrect output, or if the failure is a crash or hang, link to results.html.
     60     * If a single test had incorrect output, link to the pretty diff (e.g., http://build.webkit.org/results/Windows%20Release%20(Tests)/r71112%20(5886)/fast/blockflow/border-vertical-lr-pretty-diff.html).
     61     * If multiple tests had incorrect output, or if the failure is a crash or hang, link to the results.html for that build (e.g., http://build.webkit.org/results/Windows%20Release%20(Tests)/r71112%20(5886)/results.html).
    6662 1. Apply keywords
    6763   * `LayoutTestFailure`