Bug 151382

Summary: explicit_timeout should be false when testharness test is run in browser
Product: WebKit Reporter: youenn fablet <youennf>
Component: Tools / TestsAssignee: youenn fablet <youennf>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, commit-queue, darin, lforschler
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

youenn fablet
Reported 2015-11-18 01:17:50 PST
explicit_timeout should be false when testharness test is run in browser. This will allow timing out tests to provide a meaningful output in browser environments
Attachments
Patch (1.42 KB, patch)
2015-11-18 01:20 PST, youenn fablet 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2015-11-18 01:20:54 PST
Created attachment 265738 [details] Patch
WebKit Commit Bot
Comment 2 2015-11-19 10:19:22 PST
Comment on attachment 265738 [details] Patch Clearing flags on attachment: 265738 Committed r192633: <http://trac.webkit.org/changeset/192633>
WebKit Commit Bot
Comment 3 2015-11-19 10:19:25 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.