123585 2013-10-31 13:02:11 -0700 run-javascriptcore-tests is failing on Windows 2013-12-03 11:55:15 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P1 Normal --- 121972 1 rniwa webkit-unassigned bfulgham fpizlo ggaren mark.lam oliver roger_fong webkit-bug-importer oldest_to_newest 945645 0 rniwa 2013-10-31 13:02:11 -0700 e.g. http://build.webkit.org/builders/Apple%20Win%207%20Release%20%28Tests%29/builds/39846 http://build.webkit.org/builders/Apple%20Win%207%20Release%20%28Tests%29/builds/39846/steps/jscore-test/logs/stdio using PTY: False program finished with exit code 254 elapsedTime=1.591203 951663 1 bfulgham 2013-11-18 10:25:52 -0800 Are any of the JSC guys looking at these failures? 951701 2 ggaren 2013-11-18 11:05:58 -0800 The first step here is to build locally and get the output from the failing run. The buildbot doesn't seem to have it. 953711 3 bfulgham 2013-11-22 16:01:53 -0800 It looks like the issue is that testapi.exe fails immediately, stopping the tests from running at all. If I run "run-javascriptcore-tests --debug --no-build --no-testapi" I get a clean run: Results for Mozilla tests: 0 regressions found. 0 tests fixed. OK. 953714 4 fpizlo 2013-11-22 16:08:13 -0800 (In reply to comment #3) > It looks like the issue is that testapi.exe fails immediately, stopping the tests from running at all. > > If I run "run-javascriptcore-tests --debug --no-build --no-testapi" I get a clean run: > > Results for Mozilla tests: > 0 regressions found. > 0 tests fixed. > OK. OK, though it would be great to port the jsc-stress-tests to Windows also. The Mozilla tests don't really exercise the system. jsc-stress-tests do, and they might be able to tell you more about why testapi is failing. They'll probably reveal other bugs that aren't currently covered by layout tests, mozilla tests, or anything else. Porting run-jsc-stress-tests just involves some Windows script foo. 953728 5 bfulgham 2013-11-22 16:25:35 -0800 (In reply to comment #4) > (In reply to comment #3) > > It looks like the issue is that testapi.exe fails immediately, stopping the tests from running at all. > > > > If I run "run-javascriptcore-tests --debug --no-build --no-testapi" I get a clean run: > > > > Results for Mozilla tests: > > 0 regressions found. > > 0 tests fixed. > > OK. > > OK, though it would be great to port the jsc-stress-tests to Windows also. The Mozilla tests don't really exercise the system. jsc-stress-tests do, and they might be able to tell you more about why testapi is failing. They'll probably reveal other bugs that aren't currently covered by layout tests, mozilla tests, or anything else. > > Porting run-jsc-stress-tests just involves some Windows script foo. I'll see about getting the stress tests running under https://bugs.webkit.org/show_bug.cgi?id=124801. 956031 6 bfulgham 2013-12-03 11:55:15 -0800 These are now working properly. Closing.