On Wed, Jul 28, 2010 at 11:18:42PM +0200, Dominique Pellé wrote: > 4/ Some bugs can also be found if we test Vim on different OS. > How about keeping track of whether Vim successfully compiles and > passes all tests on: > > - Linux (x86, x86_64, ARM, MIPS, ... ) > - Windows 95, 98, NT, 2000, XP, Vista, 7 (32 & 64 bits) > - Cygwin-1.5, Cygwin-1.7 > - OS-X > - OpenBSD, HP-UX, Solaris, AIX... > - and the more exotic zOS, vms, qnx, AmigaOS, BeOS, RISC-OS (others?)
We sort of get this (at least for Linux) with the Debian packages. As
of this email, Debian's packages get built on 14 different
architectures. As part of the build, I run the test suite, albeit only
with the binary that produces the vim binary package[0]. I could look
into changing that to use a binary with the language interpreters
enabled so those portions of the test suite get run.
I monitor the build logs[1] when I upload a new version of the package
to Debian for any test failures and then triage failures. We have a
porter team for each architecture (in some state of activity) which can
be consulted if there's an architecture-specific problem that's flagged.
[0]: --enable-cscope --with-features=huge --enable-multibyte --without-x
--enable-gui=no, and --enable-gpm on linux kernels.
[1]: https://buildd.debian.org/vim
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[email protected]>
signature.asc
Description: Digital signature
