Bug 55583
| Summary: | Old websocket server process stuck around for two days on apple-windows-13 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Adam Roben (:aroben) <aroben> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | ap, bfulgham, lforschler, ukai, yutak |
| Priority: | P2 | Keywords: | PlatformOnly |
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
Adam Roben (:aroben)
apple-windows-13 had a two-day-old websocket server process running. This, in combination with bug 55581, was causing it to fail to upload test results. I killed the process on the tester, but we should figure out how to prevent this from happening in the future.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Roben (:aroben)
It looks like this started happening after a test run aborted for some reason:
http://build.webkit.org/builders/Windows%20XP%20Debug%20%28Tests%29/builds/25827 (all good)
http://build.webkit.org/builders/Windows%20XP%20Debug%20%28Tests%29/builds/25831 (test run aborted)
http://build.webkit.org/builders/Windows%20XP%20Debug%20%28Tests%29/builds/25839 (first bad run)
I think perhaps the build master was rebooted when this happened?
Anyway, regardless of the reason, we should find a way to kill old websocket servers before starting a new test run.
Brent Fulgham
We don't have this server anymore, and this bug is way to old for us to take any useful steps.