make check-dist-tarball, what does success look like?

[Martin Pool]

2009/3/23 Bob Tanner <tanner at real-time.com>:
>
> On Mar 21, 2009, at 6:08 AM, Vincent Ladeuil wrote:
>>
>>   Bob> [ascii]
>>   Bob> [ascii]
>>   Bob>
>> ----------------------------------------------------------------------
>>   Bob> [ascii] Ran 16581 tests in 3648.647s
>>
>> Eerk, one full hour !
>
> There's 1 test the looks to kick of vim and "hangs" there until I :q the
> file. The "long time" is because it sat at that screen.  Is there something
> I need to do to get a full automated run of the test suite?
>
> Is :q the right thing to do on that test?

The test suite is meant to be entirely noninteractive so if it does
this it's a bug.  It would be useful if you could use identify which
test it was by looking at the 'selftest -v' output above the point
where it runs the editor, and file a bug and put the number here.

I know some of the plugins have interactive tests but it would be much
better if they did not.   It's also a known bug that make
check-dist-tarball will run the tests of plugins you have installed in
your home directory.

-- 
Martin <http://launchpad.net/~mbp/>