Changes between Version 9 and Version 10 of WebKitGTK/Gardening/Howto


Ignore:
Timestamp:
Nov 13, 2015 5:49:33 AM (7 years ago)
Author:
clopez@igalia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebKitGTK/Gardening/Howto

    v9 v10  
    2626}}}
    27272. We pick one tests and we must research since '''when''' the test started to fail. Some ways of doing it:
    28   * '''The failure is recent (<50 releases)''': Check on the Flakiness Dashboard the recent history of each test on the buildbots.
    29     * The Flakiness Dashboard that is online (webkit-test-results.appspot.com) is very outdated regarding the list of bots. You will do better by running the flakiness dashboard locally. To do that just open with a browser the file ```Tools/TestResultServer/static-dashboards/flakiness_dashboard.html``` (it may take a bit to load even if run locally because it fetches the json files with the data from webkit.org).
     28  * '''The failure is recent (<50 releases)''': Check on the [https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html Flakiness Dashboard] the recent history of each test on the buildbots.
    3029  * '''The failure is not so recent (<200 releases)''': Manually checking the stdio log for the layout tests on the [https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20%28Tests%29?numbuilds=200 last 200 builds]. If the test passes on the older build available there , but not on the current build, then you can manually bisect the logs until you find when it started to fail. Maybe you can't find the exact release because not all releases were built or because the bot failed to compile between them. But at least you should able to allocate a shorter interval than you can bisect further by building webkit for each release on the interval and testing it.
    3130{{{