[Webkit-unassigned] [Bug 63984] new-run-webkit-tests is not correctly catching/printing TestRunInterruptedException

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jul 6 13:46:56 PDT 2011


--- Comment #1 from Dirk Pranke <dpranke at chromium.org>  2011-07-06 13:46:56 PST ---

It looks like the code mostly worked. The debug code prints the stack trace of any exception it gets on the worker. Perhaps your comment about "silently" means you wouldn't expect to see this?

But, you're right that we don't seem to be catching the exception and printing the log message, so it's unclear which code path fired on the way out.

It looks like the gtk port is running w/o multiple workers, using --worker-model=inline, so this should be trivial to test/reproduce. We have a test for this in run_webkit_tests_integrationtest.py: test_exit_after_n_crashes that you can probably debug or try on the command line to see what happens.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list