Bug 197820 - When run from Xcode, webkittestrunner always seems to have an m_timeout of zero
Summary: When run from Xcode, webkittestrunner always seems to have an m_timeout of zero
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-05-11 15:47 PDT by Simon Fraser (smfr)
Modified: 2019-05-16 08:23 PDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 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.
Comment 1 Simon Fraser (smfr) 2019-05-11 15:48:07 PDT 
TestInvocation::initializeWaitToDumpWatchdogTimerIfNeeded() is always starting the watchdog timer with zero seconds.
Comment 2 Radar WebKit Bug Importer 2019-05-11 15:48:25 PDT 
<rdar://problem/50697654>
Comment 3 Simon Fraser (smfr) 2019-05-16 08:23:59 PDT 
This is by design. Pass --no-timeout to get around it.