172371 2017-05-19 11:51:17 -0700 Speedometer 2.0: stops at test 32 2017-05-23 12:48:10 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED CONFIGURATION CHANGED https://bugs.webkit.org/show_bug.cgi?id=172339 InRadar P2 Normal --- 172339 1 bbouvier+webkit webkit-unassigned addyo bbouvier+webkit lforschler rniwa webkit-bug-importer oldest_to_newest 1310693 0 bbouvier+webkit 2017-05-19 11:51:17 -0700 STR: - clone latest webkit repository - go to PerformancesTests/Speedometer - serve (python -m SimpleHTTPServer) and visit in a browser I'd expect the benchmark to finish, but it doesn't at the moment because test #32 tries to load /resources/todomvc/architecture-examples/preact/build/index.html, when the actual URI should be /resources/todomvc/architecture-examples/preact/dist/index.html (note the build => dist). It causes a 404 and the benchmark runner doesn't terminate. 1311179 1 webkit-bug-importer 2017-05-21 16:59:59 -0700 <rdar://problem/32319159> 1311184 2 rniwa 2017-05-21 17:56:49 -0700 Hm... I'm not seeing this. https://trac.webkit.org/browser/webkit/trunk/PerformanceTests/Speedometer/resources/tests.js?rev=217198#L355 says: todomvc/architecture-examples/preact/dist/index.html which revision of WebKit did you check out? 1311262 3 bbouvier+webkit 2017-05-22 02:13:16 -0700 I was using 4e56588e6e0b54becfc891fc5f111f61ed57f87c, but it seems the issue has been fixed in the meanwhile: running on trunk terminates now. Thanks! 1311588 4 rniwa 2017-05-22 14:53:11 -0700 Maybe you can shed a light on https://bugs.webkit.org/show_bug.cgi?id=172439. Firefox's score goes up by 40% on Speedometer 2 compared to 1, and we're afraid something might be broken in Firefox. 1311803 5 bbouvier+webkit 2017-05-23 02:49:48 -0700 Sorry, I have no idea at this time. I've been running the benchmark and it doesn't seem anything goes wrong, since the benchmark properly terminates. Is there any error checking in this benchmark, i.e. checks against expected results? 1311996 6 rniwa 2017-05-23 12:48:10 -0700 No, there is no error checking. We'll investigate it further on https://bugs.webkit.org/show_bug.cgi?id=172439