Bug 172371
| Summary: | Speedometer 2.0: stops at test 32 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Benjamin Bouvier <bbouvier+webkit> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | addyo, bbouvier+webkit, lforschler, rniwa, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=172339 | ||
| Bug Depends on: | |||
| Bug Blocks: | 172339 | ||
Benjamin Bouvier
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/32319159>
Ryosuke Niwa
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?
Benjamin Bouvier
I was using 4e56588e6e0b54becfc891fc5f111f61ed57f87c, but it seems the issue has been fixed in the meanwhile: running on trunk terminates now. Thanks!
Ryosuke Niwa
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.
Benjamin Bouvier
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?
Ryosuke Niwa
No, there is no error checking. We'll investigate it further on https://bugs.webkit.org/show_bug.cgi?id=172439