Changes between Version 122 and Version 123 of WebKitGTK/KeepingTheTreeGreen


Ignore:
Timestamp:
Jul 25, 2017 4:25:07 AM (4 years ago)
Author:
clopez@igalia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebKitGTK/KeepingTheTreeGreen

    v122 v123  
    11(courtesy of Martin Robinson, who introduced the notion of Garderner in WebKit world of fame)
    22
    3 1. Keep the tree green: the gardener on a given day will diagnose all bot redness and try to form a hypothesis for each failure. In my experience there are several types of failures:
     31. Keep [https://build.webkit.org/waterfall?category=GTK the tree green]: the gardener on a given day will diagnose all bot redness and try to form a hypothesis for each failure. In my experience there are several types of failures:
    44  a. The GTK+ port is lacking some feature or has a bug: In this case the gardener will figure out exactly what the problem is, open a bug with as much information as possible including test diffs and links to relevant bugs. The gardener will CC any people involved in WebKitGTK+ who would might know how to fix the problem.
    55  b. A test is exposing a general WebKit bug that only GTK+ triggers (often the case with JavaScriptCore and inspector tests): In this case the gardener will leave a comment on the original bug with the test diff or stack trace (for something like an assertion failure) and offer to gather more information for the original patch author (even resorting to debugging directly on the bots if it cannot be reproduced locally).