Sheriffing/How To/Intermittent bugs: Difference between revisions

Sheriffing/How To/Intermittent bugs (view source)

Revision as of 13:49, 19 July 2018

1,379 bytes added , 19 July 2018

explained test-verify backfill

Archaeopteryx

Confirmed users

571

edits

@@ Line 5: / Line 5: @@
 [[File:Treeherder suggestion.png|Treeherder suggestions]]
+= Check for intermittency =
+'''Don't retrigger or backfill build jobs or gecko decision tasks, only tests.'''
+If you are not sure if a failure line is a new frequent failure or even a perma-failure and require a backout of the change which causes the failure, you can request more runs of the job:
+* On the same push ("retrigger") by pressing the '''r''' key or clicking the button (circular arrow).
+* On previous pushes by opening the actions menu in the bottom toolbar ("...") and and calling "Backfill". This will run the job on the 5 previous pushes, independent if it already ran for those pushes or not. If the job depends on a build which is missing, that build will be generated before the test runs.
+** A quicker way - if supported - to check if this fails frequently is test-verify backfill.
+**# Get the full path and name of the failing job, e.g. with dxr.mozilla.org and copy it into the clipboard.
+**# From the action menu at the bottom ("..."), select 'Custom action'
+**#* Set "inclusive" to true
+**#* Set "depth" to 1 (to run it on the current push and only the one before).
+**#* Add "testPath:" and the test path and name from the clipboard.
+**# The test will be run multiple times in a job TV-bf. If it fails for the later job but passes for the previous one, it is a strong indicator that the failure is related to changes of the push with the TV-bf failure.
 = How to file a bug for an intermittent failure =