Summary: | [Win] run-jsc-stress-tests failures | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Brent Fulgham <bfulgham> | ||||
Component: | JavaScriptCore | Assignee: | Brent Fulgham <bfulgham> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | bfulgham, fpizlo, joepeck, mark.lam, mhahnenberg, msaboff, ossy, peavo | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Bug Depends on: | 125111 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Brent Fulgham
2013-12-03 15:19:39 PST
The sunspider tests may be failing due to path issues. The test harness is run from Cygwin, but the JSC executable is a Windows binary that expects paths to be in DOS/Windows format. If I modify the "run-jsc-stress-tests" to pass a Windows-style path to the test input, I now get a series of files containing ">quit" in them. Created attachment 218368 [details]
Patch
The attached patch gets things working, but may not be good idiomatic Ruby code. With this patch, I get the following results: ** The following JSC stress test failures have been introduced: jsc-layout-tests.yaml/js/script-tests/math.js.layout jsc-layout-tests.yaml/js/script-tests/math.js.layout-no-llint jsc-layout-tests.yaml/js/script-tests/math.js.layout-no-cjit jsc-layout-tests.yaml/js/script-tests/math.js.layout-dfg-eager-no-cjit jsc-layout-tests.yaml/js/script-tests/sort-stability.js.layout jsc-layout-tests.yaml/js/script-tests/sort-stability.js.layout-no-llint jsc-layout-tests.yaml/js/script-tests/sort-stability.js.layout-no-cjit jsc-layout-tests.yaml/js/script-tests/sort-stability.js.layout-dfg-eager-no-cjit Results for JSC stress tests: 8 failures found. It doesn't seem like the profiling output is being incorporated into the "failure" part of the testing. Comment on attachment 218368 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=218368&action=review > Tools/Scripts/run-jsc-stress-tests:87 > + if $? == 0 > + $isCygwin = 1 > + else > + $isCygwin = 0 > + end How about: $isCygwin = $? == 0 Also, in Ruby booleans are distinct from numbers (unlike, e.g., perl). > Tools/Scripts/run-jsc-stress-tests:89 > + $isCygwin = 0 $isCygwin = false > Tools/Scripts/run-jsc-stress-tests:596 > + if $isCygwin == 1 if $isCygwin I'm surprised that this is the only place where you need to do this. I guess profilerOutput is the only absolute path generated by the script? If so it might make sense to just change this to a relative path so that we don't need any cygwin specific stuff. Windows bots already run jsc stress tests long long time ago. Clearing review flag, this bug has already been marked as closed anyways. |