Confirmed users
571
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
Jump to navigation
Jump to search
→Manually filing a bug: added information how to identify component for crashes
(→Check for intermittency: add permafail dashboard) |
(→Manually filing a bug: added information how to identify component for crashes) |
||
| Line 58: | Line 58: | ||
In this case, we get: <code>Core :: DOM<br> | In this case, we get: <code>Core :: DOM<br> | ||
testing/web-platform/tests/navigation-timing/test_timing_xserver_redirect.html</code> | 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: | |||
### Check if the crash signature itself discloses were the bug belongs, e.g. <code>[@ webrtc::MouseCursorMonitorX11::CaptureCursor()]</code> goes into <code>Core :: WebRTC</code>. | |||
### In case it's not obvious from the crash signature, check the crashing thread. The files mentioned for the first numbers ("stack frame") can be from managing the crash (e.g. contain "report"). Skip those. After you find one which looks like "real" code, look up the component like mentioned above. | |||
# Copy the failure text from the log window into the bug | # 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 | # Set the Summary as: Intermittent navigation-timing/test_timing_xserver_redirect.html | expected OK | ||