Bug 161257 - Database process crash was copied, but didn't get into Other Crashes
Summary: Database process crash was copied, but didn't get into Other Crashes
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Jonathan Bedard
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-26 12:27 PDT by Alexey Proskuryakov
Modified: 2017-02-21 16:25 PST (History)
4 users (show)

See Also:


Attachments
Patch (1.71 KB, patch)
2016-08-26 15:03 PDT, Jonathan Bedard
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2016-08-26 12:27:36 PDT
I see a Database process crash here <https://build.webkit.org/results/Apple%20Yosemite%20Debug%20WK2%20(Tests)/r205023%20(14606)/>, but it's not in results.html: <https://build.webkit.org/results/Apple%20Yosemite%20Debug%20WK2%20(Tests)/r205023%20(14606)/results.html>.

This seems strange, clearly webkitpy knew about this crash if it copied it.
Comment 1 Jonathan Bedard 2016-08-26 14:10:50 PDT
Here is the standard out for this test: https://build.webkit.org/builders/Apple%20Yosemite%20Debug%20WK2%20%28Tests%29/builds/14606/steps/layout-test/logs/stdio

What is very strange about this particular error is that the crash file has a timestamp of "2016-08-25 15:00:37.971," meaning this particular crash file started generating the previous afternoon.  There is a possibility that https://bugs.webkit.org/show_bug.cgi?id=161218 would fix this bug.

There is also a strong likely-hood that this bug has to do with bot184 and bot185 being restarted this morning.
Comment 2 Jonathan Bedard 2016-08-26 14:40:08 PDT
Layout-test-results is deleted after it is archived during archive-test-results.  We should delete it when we remove stale test results as well.
Comment 3 Jonathan Bedard 2016-08-26 15:03:32 PDT
Created attachment 287154 [details]
Patch
Comment 4 Jonathan Bedard 2017-02-21 16:25:56 PST
This has not been an issue since.

It seems this bug was caused by the bots being interrupted in the middle of their test run.