Confirmed users
571
edits
(→Manually filing a bug: added information how to identify component for crashes) |
|||
Line 54: | Line 54: | ||
## 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]. If you don't find anything, then there are still folders from outside the source folder in the path. Delete everything e.g. up to 'gecko' or 'build' and try again. | ## 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]. If you don't find anything, then there are still folders from outside the source folder in the path. Delete everything e.g. up to 'gecko' or 'build' and try again. | ||
## Copy the full folder and file path, e.g. <code>testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code> | ## 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: | ## 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: <code>./mach file-info bugzilla-component testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code> In this case, we get: <code>Core :: DOM<br>testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code> | ||
<code>./mach file-info bugzilla-component testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code> | |||
In this case, we get: <code>Core :: DOM<br> | |||
testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code> | |||
## If the failure is real crash (not a crash report because the test execution hang and the application eventually has to be shut down), try to identify the component from the crash: | ## If the failure is real crash (not a crash report because the test execution hang and the application eventually has to be shut down), try to identify the component from the crash: | ||
### Check if the crash signature itself discloses were the bug belongs, e.g. <code>[@ webrtc::MouseCursorMonitorX11::CaptureCursor()]</code> goes into <code>Core :: WebRTC</code>. | ### Check if the crash signature itself discloses were the bug belongs, e.g. <code>[@ webrtc::MouseCursorMonitorX11::CaptureCursor()]</code> goes into <code>Core :: WebRTC</code>. |