Sheriffing/How To/Intermittent bugs: Difference between revisions

Sheriffing/How To/Intermittent bugs (view source)

Revision as of 16:23, 6 November 2017

1,119 bytes added , 6 November 2017

added identification fo bugzilla product and component with |./mach file-info| to bug filing how-to

Archaeopteryx

Confirmed users

571

edits

@@ Line 8: / Line 8: @@
 = How to file a bug for an intermittent failure =
-If there's no bug on file, you'll need to file one. The are two requirements need to be included in the bug that this bug can be displayed automatically by Treeheder when this intermittent failure happens again:
+If there's no bug on file, you'll need to file one.
+== Bugfiler ==
+If bugfiler isn't automatically enabled for you, you can add <code>&bugfiler</code> to the Treeherder url, e.g. https://treeherder.mozilla.org/#/jobs?repo=autoland&bugfiler This activates bugfiler (the little bug icon beside a failure) that automates most of the manual steps from the previous section.
+The are two requirements need to be included in the bug that this bug can be displayed automatically by Treeheder when this intermittent failure happens again:
 # In the summary: '''Intermittent''' test_file test failure
 # In the Keyword field choose the keyword: '''intermittent-failure'''
-== Example ==
+== Manually filing a bug ==
-Lets imagine you have a test failure like <code>TEST-UNEXPECTED-TIMEOUT | /navigation-timing/test_timing_xserver_redirect.html | expected OK</code> in Treeherder and there is no bug on file for this failure.
+Lets imagine there are issues with bugfiler or you can't use it for other reasons (e.g. security sensitive bug which should not be public) and you have a test failure like <code>TEST-UNEXPECTED-TIMEOUT | /navigation-timing/test_timing_xserver_redirect.html | expected OK</code> in Treeherder and there is no bug on file for this failure.
 # Open the Treeherder Log
 # Login into Bugzilla in a different tab/window
 # Find the Product/Component where you need to file this bug (note: dxr and hg.mozilla.org can be very helpful if you are in doubt)
-#* In this example the Bug belong to Core:Document Navigation
+## Copy the file path from the failure line <code>/navigation-timing/test_timing_xserver_redirect.html</code>
+## Find it in the repository, either with the search term 'path:/navigation-timing/test_timing_xserver_redirect.html' on [https://dxr.mozilla.org/mozilla-central/source/ DXR] or '/navigation-timing/test_timing_xserver_redirect.html' in the right path filter field of [http://searchfox.org/ searchfox].
+## Copy the full folder and file path, e.g. <code>testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code>
+## In the console with the mozilla-unified folder, run the following command to get the Bugzilla product and component in which bugs related to the file should be posted:<br>
+<code>./mach file-info bugzilla-component testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code><br>
+In this case, we get: <code>Core :: DOM<br>
+testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code>
 # Copy the failure text from the log window into the bug
 # Set the Summary as: Intermittent navigation-timing/test_timing_xserver_redirect.html | expected OK
@@ Line 29: / Line 40: @@
 Treeherder syncs with Bugzilla several times a day. Once your bug is added and the systems sync, Treeherder will suggest your new bug as a match for the next intermittent failure of this type.
-= Bugfiler =
-You can add <code>%bugfiler</code> to the Treeherder url, e.g. https://treeherder.mozilla.org/#/jobs?repo=autoland&bugfiler This activates bugfiler (the little bug icon beside a failure) that automates most of the manual steps from the previous section.