Summary: | x11perf test run aborting | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | zy <yan.z.zhang> | ||||
Component: | Server/General | Assignee: | Keith Packard <keithp> | ||||
Status: | VERIFIED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | major | ||||||
Priority: | high | CC: | gordon.jin, nian.wu | ||||
Version: | git | ||||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
zy
2007-05-22 18:47:00 UTC
Created attachment 10074 [details]
datafile
Why do you use Xmark? you should just use x11perfcomp. x11perfcomp is used to compare several x11perf result. It will skip the failed case. Xmark can give a performance number against single x11perf result. If x11perf abort, Xmark will report this problem. Anyway, we will run x11perf again with the latest source. x11perfcomp can be used on single data to get speed number, although -r/-ro has no effect then. What's your repeat time? your have 413 'trep' result, which Xmark script will refuse as it only agrees on 441 or 447 results. Not sure what's wrong. It's XMark issue. Now we are suggested to use x11perfcomp to compare performance data, not Xmark. So don't care about Xmark. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.