Summary: | 26 MotionMark performance tests failing | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Ryan Haddad <ryanhaddad> | ||||
Component: | New Bugs | Assignee: | Said Abou-Hallawa <sabouhallawa> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, cdumez, commit-queue, glenn, jonlee, rniwa, sabouhallawa, simon.fraser | ||||
Priority: | P2 | ||||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Ryan Haddad
2017-01-09 11:13:34 PST
It seems all the MotionMark tests did not run. How do these tests run on the webkit bots? Do we use Tools/Scripts/run-benchmark to run them? (In reply to comment #1) > It seems all the MotionMark tests did not run. How do these tests run on the > webkit bots? Do we use Tools/Scripts/run-benchmark to run them? In this case they seem to be running with Tools/Scripts/run-perf-tests I just realized that Animometer had never run on the WebKit bots. It was skipped in the file PerformanceTests/Skipped. When the name was changed to MotionMark, it runs by default which we don't want. The fix is to skip MotionMark instead of Animometer in PerformanceTests/Skipped. Created attachment 298811 [details]
Patch
Comment on attachment 298811 [details] Patch Clearing flags on attachment: 298811 Committed r210757: <http://trac.webkit.org/changeset/210757> All reviewed patches have been landed. Closing bug. |