[Webkit-unassigned] [Bug 153217] New: Layout tests get waiting forever when the abort early count triggers.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=153217

            Bug ID: 153217
           Summary: Layout tests get waiting forever when the abort early
                    count triggers.
    Classification: Unclassified
           Product: WebKit
           Version: Other
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Major
          Priority: P1
         Component: Tools / Tests
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: clopez at igalia.com
                CC: bugs-noreply at webkitgtk.org, lforschler at apple.com

When the layout tests abort early because any of:

--exit-after-n-failures 500 
--exit-after-n-crashes-or-timeouts 50

The run-webkit-tests don't exits, but it gets stalled waiting forever.

This can be seen for example on this log: https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Debug%20%28Tests%29/builds/6641/steps/layout-test/logs/stdio

[...]
16:38:47.334 13734 worker/2 cleaning up
16:38:47.334 13734 worker/2 cleaning up
16:38:47.339 13734 worker/3 cleaning up
16:38:47.339 13734 worker/3 cleaning up
16:38:47.345 13734 worker/4 cleaning up
16:38:47.345 13734 worker/4 cleaning up
16:38:47.350 13734 worker/5 cleaning up
16:38:47.350 13734 worker/5 cleaning up
16:38:47.363 13734 Exiting early after 20 crashes and 30 timeouts. 31033 tests run.   <--- Here triggers the --exit-after-n-crashes-or-timeouts 50
16:38:47.363 13734 Stopping HTTP server ...
16:38:47.364 13734 Attempting to shut down httpd server at pid 13767
16:38:47.439 13734 Waiting for action: <function <lambda> at 0x7ffdc8347050>
16:38:48.440 13734 httpd server at pid 13767 stopped
16:38:48.440 13734 Stopping WebSocket server ...
16:38:48.440 13734 Attempting to shut down pywebsocket server at pid 13773
16:38:48.440 13734 Waiting for action: <bound method PyWebSocket._check_and_kill of <webkitpy.layout_tests.servers.websocket_server.PyWebSocket object at 0x7ffdc83284d0>>
16:38:49.440 13734 Waiting for action: <bound method PyWebSocket._check_and_kill of <webkitpy.layout_tests.servers.websocket_server.PyWebSocket object at 0x7ffdc83284d0>>
16:38:50.441 13734 pywebsocket server at pid 13773 stopped
16:38:50.441 13734 Stopping Web Platform Test server ...
16:38:50.441 13734 Attempting to shut down wptwk server at pid 13775
16:38:50.441 13734 Stopping wptwk server
16:38:50.441 13734 Cleaning WPT resources files
16:38:50.442 13734 Cleaning WPT web platform server config.json
16:38:50.456 13734 wptwk server at pid 13775 stopped
16:38:50.469 13734 Flushing stdout
16:38:50.469 13734 Flushing stderr
16:38:50.469 13734 Stopping helper
16:38:50.469 13734 Cleaning up port
16:38:50.486 13734 Restoring module-stream-restore failed
[...]


------------------------------------------------------------------------------

command timed out: 1200 seconds without output, killing pid 13733                   <--- it gets killed after the 1200 max timeout for any step on the bots is reached
process killed by signal 9
program finished with exit code -1
elapsedTime=3368.105984


This can be reproduced be easily reproduced by running the tests with any of

--exit-after-n-failures 2 
--exit-after-n-crashes-or-timeouts 2

It happens both with release and debug builds.

It affects the GTK port, and probably all the other ports (didn't tested).

This is causing unusual long test runs on the GTK debug test bot.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160119/aa79abe9/attachment.html>