Bug 197820

Summary:	When run from Xcode, webkittestrunner always seems to have an m_timeout of zero
Product:	WebKit	Reporter:	Simon Fraser (smfr) <simon.fraser>
Component:	Tools / Tests	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED FIXED
Severity:	Normal	CC:	ap, lforschler, simon.fraser, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	WebKit Nightly Build
Hardware:	Unspecified
OS:	Unspecified

Simon Fraser (smfr)

Reported 2019-05-11 15:47:35 PDT

I've set up an Xcode scheme for the WebKitTestRunner executable to run it, passing the full path to the test. The test uses waitUntilDone/notifyDone(), but WTR's watchdog fires immediately so the test always ends prematurely. In TestInvocation, m_timeout is always zero, even if --timeout is passed.

Attachments
Add attachment proposed patch, testcase, etc.

Simon Fraser (smfr)

Comment 1 2019-05-11 15:48:07 PDT

TestInvocation::initializeWaitToDumpWatchdogTimerIfNeeded() is always starting the watchdog timer with zero seconds.

Radar WebKit Bug Importer

Comment 2 2019-05-11 15:48:25 PDT

<rdar://problem/50697654>

Simon Fraser (smfr)

Comment 3 2019-05-16 08:23:59 PDT

This is by design. Pass --no-timeout to get around it.

Note You need to log in before you can comment on or make changes to this bug.