diff options
Diffstat (limited to 'non-puppet/qtmetrics/ci/msgprojectdashboardlevel2.html')
| -rw-r--r-- | non-puppet/qtmetrics/ci/msgprojectdashboardlevel2.html | 111 |
1 files changed, 0 insertions, 111 deletions
diff --git a/non-puppet/qtmetrics/ci/msgprojectdashboardlevel2.html b/non-puppet/qtmetrics/ci/msgprojectdashboardlevel2.html deleted file mode 100644 index bce0469..0000000 --- a/non-puppet/qtmetrics/ci/msgprojectdashboardlevel2.html +++ /dev/null @@ -1,111 +0,0 @@ -<!DOCTYPE html> -<html> - <head> - <meta charset="UTF-8"> - <link rel="stylesheet" type="text/css" href="../styles.css" /> - <link rel="shortcut icon" href="../images/favicon.ico" type="image/x-icon" /> - <title>Qt Metrics Information</title> - </head> - - <body class="messageWindow"> - <img src="../images/info.png" alt="info"><br><br> - - <!-- The message or content to be shown on new window --> - <p><b><u>PROJECT DASHBOARD DESCRIPTION:</u></b></p> - <p><b>Level 2: Show Project build information</b></p> - <table> - <tr> - <th class="tableCellAlignLeft">GENERAL</th><td></td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Purpose</th> - <td class="tableSingleBorder">Improve Continuous Integration (CI) stability, throughput and coverage by fixing Autotests and Configuration builds</td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Question</th> - <td class="tableSingleBorder">Is the Project build constantly failing, and how Autotest and Configuration build settings (force success, significance) affect to results.<br> - How long do the Builds take to execute, and are the different Configurations run effectively in parallel.</td> - </tr> - <tr><td> </td><td></td></tr> - <tr> - <th class="tableCellAlignLeft">METRIC</th><td></td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Filters</th> - <td class="tableSingleBorder">Project, Platform, Configuration, Timescale</td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Indicator</th> - <td class="tableSingleBorder">Project build information, build history, list of Configuration builds, and list of failed Autotests that caused build failure (significant Autotests in blocking Configurations)</td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Calculation</th> - <td class="tableSingleBorder"><b>Build information:</b> Showing data for the build (no calculation)<br> - <b>Build history:</b> Showing a few last Project builds with date, result and link to source build results directory (no calculation). - By default, the latest Build data is shown, but any listed Build can be selected by clicking the build number. - The Timescale filtered and/or the Build selected is indicated.<br> - <b>Configurations:</b> Showing the Configuration build result and tagging (force success, significance), - the count and ratio of failed Autotests by significance with the number of reruns for the latest build, - and the count and ratio of failed and successful builds compared to total for each Configuration - (either based on all data in the database or according to the Timescale filter i.e. based on the builds done after the selected date).<br> - <i>Note: The sum of failed and successful builds may not match with the total because, in case some already running Configuration build fails, the possibly waiting builds are cancelled (seen with result "undef" in the list).</i><br> - <b>Build phases:</b> Showing the Configuration build execution by phases in the order of execution from their start time to end time.<br> - <b>Failed Autotests:</b> Showing the list of failed significant Autotests in blocking Configurations i.e. the ones that caused the Project build failure (combined list of related failed Autotests from each Configuration build). - </td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Interpretation</th> - <td class="tableSingleBorder"><b>Build information:</b> Note that the build duration may show 00:00:00 for failed builds<br> - <b>Build history:</b> Successive failures or sudden failure after successive successful builds indicate a need for analysis<br> - <b>Configurations:</b> Builds with force success tagging should be understood. - Builds with insignificant tagging should be analyzed, especially if there are several failed significant Autotests. - High count, ratio or number of reruns of failed Autotests indicates a need for analysis. - High ratio of failed builds compared to successful builds indicates a need for analysis. - <i>Note: The ratio may not be an ideal measure when the total count of builds is low.</i><br> - <i>Tip: The Autotest dashboard can be utilized here in parallel with the Project dashboard.</i><br> - <b>Build phases:</b> The shorter time the better. The less idle time before starting or between the phases the better.<br> - <b>Failed Autotests:</b> The failed Autotests that caused build failure should be analyzed.<br> - <i>Tip: The Autotest dashboard can be utilized here in parallel with the Project dashboard.</i> - </td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Target value</th> - <td class="tableSingleBorder">Successful builds with not any failed Autotests and with not any tagged (force success, insignificant) Configurations</td> - </tr> - <tr><td> </td><td></td></tr> - <tr> - <th class="tableCellAlignLeft">DATA</th><td></td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Data items</th> - <td class="tableSingleBorder"><b>Project:</b> e.g. QtBase_stable_Integration; Project filter uses the name part "QtBase" and Branch filter uses the branch part "stable"<br> - <b>Build number:</b> several per Project (numeric 1 to n; number is Project specific)<br> - <b>Build result:</b> SUCCESS/FAILURE/undef ("undef" means the build was cancelled before it was even started because some other Configuration build failed and caused the whole Project build failure)<br> - <b>Build date:</b> date and time when build started<br> - <b>Build duration:</b> build duration in hh:mm:ss (may show 00:00:00 for failed builds)<br> - <b>Build phases:</b> phase name, start timestamp and end timestamp<br> - <b>Configuration:</b> several per Project Build (e.g. linux-g++-32_Ubuntu_10.04_x86); Platform filter uses predefined searches to the Configuration name<br> - <b>Configuration force success:</b> Yes/- (if tagged as "force success" the Configuration build is forced to succeed, so that it will not block the whole Project build; this is e.g. in case of a new or immature Configuration when it is not reasonable to let the whole Project build fail because of this specific Configuration)<br> - <b>Configuration insignificant:</b> Yes/- (if tagged as "insignificant" the Configuration build will not fail even though some significant Autotests would fail)<br> - <b>Autotest name:</b> several per Configuration (e.g. tst_qftp)<br> - <b>Autotest significance:</b> number of failed Autotests with tagging Significant (failure leads to build failure, unless the Configuration set insignificant) / Insignificant (failure does not lead to build failure)<br> - <b>Autotest runs:</b> number of times the Autotest was run in a build (more than one means it was rerun to see if it is flaky) - </td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Data source</th> - <td class="tableSingleBorder">Data in SQL database from log files in http://testresults.qt.io/ci/</td> - </tr> - <tr> - <th class="tableCellBackgroundTitle tableCellAlignLeft tableSingleBorder">Data update cycle</th> - <td class="tableSingleBorder">New builds are updated to database in real time</td> - </tr> - </table> - <!-- End of message --> - - <br><br> - <button type="button" onclick="window.open('', '_self', ''); window.close();">Close</button> - <br><br> - - </body> -</html>
\ No newline at end of file |