Changes between Version 3 and Version 4 of TriagingTestFailures

Timestamp:

Nov 2, 2010, 9:32:41 AM (14 years ago)

Author:

Adam Roben

Comment:

Address some of John Sullivan's feedback

TriagingTestFailures

@@ -47 +47 @@
      * No: there might be some existing platform-specific code that is responsible for the different results.
 
-= Group failures by "root cause" =
+= File bugs for the failures =
 
-If a multiple tests are all failing for the same reason, they should be grouped together into a single root cause.
-
-= File one or more bugs for each root cause =
-
-If a test fails on multiple platforms and those platforms will need separate fixes, you should file one bug for each failing platform.
+If 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.
 
  1. Go to http://webkit.org/new-bug
  1. Include in your report:
    * The name(s) of the failing test(s)
-   * The root cause you determined, if any
+   * The reason you determined for the failure, if any
    * What platform(s) the failures occur on
    * When the failures began, if known
    * A link to the failing output
-     * If a single test had incorrect output, link to the pretty diff.
-     * If multiple tests had incorrect output, or if the failure is a crash or hang, link to results.html.
+     * 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).
+     * 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).
  1. Apply keywords
    * `LayoutTestFailure`