>> With respect to running the actual test, I think that editing
>> include/have_innodb.inc to force innodb to appear present without
>> actually using it would cause more tables and more tests to run on
>> Falcon. Having such an edit would require that this test is run off a
>> local tree that has this change in place. Before every run, just do "bzr
>> pull" to bring the latest Falcon changes in while keeping the hacked
>> test files.
> Finding a machine to run this and do it on a regular schedule is not a
> problem - I (we) have a couple of hosts available for this kind of thing
> in the TRD lab. The main issue is finding the time to analyze the
> results, in relation to other priorities we have.
I estimate the effort at way less than 1 hour per week (I have done it a
couple of times myself). I think that the amount of extra testing coverage
that is obtained that way is sufficient to justify the time spent.