Bazaar back into Pybots?

[Alexander Belchenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool пишет:
> Ian was working on setting up buildbot Robert reminded me that there
> is a project at python.org that tests the python interpreter on
> various platforms on various python modules.
>
>  http://www.pybots.org/
>
> There is a machine there which claims to be building Bazaar on Windows
> but I think it's now inactive.  It would be good to find out ahead of
> time about any breakage of Bazaar by python2.5 or 2.6 releases,
> although there may be some noise from breakage just inside python.  It
> may also get some useful exposure of Bazaar to python developers.
>
> So I'd suggest: seeing if there's someone currently running a machine
> who would also test Bazaar, otherwise contributing a machine we run
> that will test Bazaar on Windows and Ubuntu.

I time-to-time run selftest on my machine, and I can say, that selftest
*never* run without fails or errors on Windows. Even when John fix (almost)
all win32-related issues before 0.8 release, it degrades very quickly.

Last time (before 0.16 release) there was less than 20 errors on Python 2.5
with all dependencies installed (medusa, paramiko, pycurl, diffutils,
gettext). Most of the failing tests was because of locking problem.
And this test is completely ugly:
test_lockdir.TestLockDir.test_35_wait_lock_changing -- it fails only
when running in the middle of test suite, but *never* when running
alone or with --first flag. Probably it should say something important?

Note that 2.5.1 introduce regression in our test suite because many
OSError now becomes WindowsErrors with all bad side effects.

Also side effect of regular running bzr selftest: it read/write very
big amount of data (files, directories) on HDD, as result HDD degrades
very quickly. Usual disks, especially in laptops, is really not designed
for instant loading. Recently I read about machines that used for
regular testing of pypy project: they have broken and exchanged during
warranty period. If we can reduce our disk I/O load and do most of testing
in memory itself -- it will be good, IMO.

[µ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGQD6xzYr338mxwCURAkZtAJwIETlJj+JI36iuwgKHbY3QwhI92QCfe86i
lU6vgSHG4Pqh6vJxES45BeE=
=SeMN
-----END PGP SIGNATURE-----