> Public bug reported:
>
> In order to track multi-touch latency over time, we need to be able to
> run scripts that gather it (see bug #622753) and then store this data
> with date/time stamps. We will use this information to determine overall
> improvements in performance as well as identify regressions early in the
> development process.
>
> The Hudson testing tool will likely be a very good fit for this.
> Integration with Hudson should be coordinated with Martin Pool and
> Robert Collins.
Yeah, I have actually used Hudson before. Not bad at all, although I never
figured out how well it works for multiple architectures.
On 08/23/2010 04:25 PM, Duncan McGreggor wrote:
[...]
> Public bug reported:
>
> In order to track multi-touch latency over time, we need to be able to
> run scripts that gather it (see bug #622753) and then store this data
> with date/time stamps. We will use this information to determine overall
> improvements in performance as well as identify regressions early in the
> development process.
>
> The Hudson testing tool will likely be a very good fit for this.
> Integration with Hudson should be coordinated with Martin Pool and
> Robert Collins.
Yeah, I have actually used Hudson before. Not bad at all, although I never
figured out how well it works for multiple architectures.
Henrik