Bug 124846

Summary: Disable JSC stress tests on all but Apple-Mac platforms
Product: WebKit Reporter: Mark Hahnenberg <mhahnenberg>
Component: JavaScriptCoreAssignee: Mark Hahnenberg <mhahnenberg>
Status: RESOLVED INVALID    
Severity: Normal CC: zan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 120809    
Attachments:
Description Flags
Patch none

Mark Hahnenberg
Reported 2013-11-25 10:19:31 PST
Recent changes to how run-jsc-stress-tests works have made it so other platforms can't run any JSC tests. We should disable run-jsc-stress-tests on those platforms until they have ported the changes to their platforms. For now they'll fall back on the old run-javascriptcore-tests harness.
Attachments
Patch (1.42 KB, patch)
2013-11-25 10:22 PST, Mark Hahnenberg 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Mark Hahnenberg
Comment 1 2013-11-25 10:22:32 PST
Created attachment 217815 [details] Patch
Zan Dobersek
Comment 2 2013-12-02 13:42:47 PST
The GTK port is currently running the stress tests without problems. http://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release/builds/42895/steps/jscore-test/logs/stdio Is this patch still valid? Does it depend on any future patch? If so, can you please provide some pointers, especially on what's required to re-enable the stress tests in the future if they get disabled when this lands?
Mark Hahnenberg
Comment 3 2013-12-02 13:43:41 PST
(In reply to comment #2) > The GTK port is currently running the stress tests without problems. > http://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release/builds/42895/steps/jscore-test/logs/stdio > > Is this patch still valid? Does it depend on any future patch? > If so, can you please provide some pointers, especially on what's required to re-enable the stress tests in the future if they get disabled when this lands? Sorry, no longer needed. I retrofitted the other patch so that it works on other platforms.
Note You need to log in before you can comment on or make changes to this bug.