Bazaar back into Pybots?

[Alexander Belchenko]

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

Martin Pool пишет:
> On 5/8/07, Alexander Belchenko <bialix at ukr.net> wrote:
>> 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?
> 
> OK, well automated running is probably only going to help us stay
> clean once we are clean.  How can we get there?  Just pay good
> attention to Alexander, or have other people run the tests
> interactively themselves?  If so, maybe automated running is not a
> priority yet?

I think selftest is REALLY REALLY REALLY good thing.
But it cost too much efforts to keep it clean on Windows, really.
I try to keep it, you know, but dedicated win32 server that runs selftest
*regularly* and *all* core developers will look at their result --
it will be the best for me.

Currently selftest fails because of false positives or just platform limitations.
And in last order it's the real platform regression.
Without real access to Windows machine no one can easily debug such problems.

So, such testing server will help, especially we lacks this tool when
dirstate was landed and then after fact John fix win32 regressions.
So this win32 server should be able to run tests not only in bzr.dev,
but let any core developer run tests in their own development branch
with new and experimental features to see how it impacts windows behavior.

That's my opinion.

[µ]


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

iD8DBQFGQEohzYr338mxwCURAgTNAJ9hTXWB1+vZfddtszHDxC8p2wdSDwCfTtd5
hZaZnBCP2djLRJ4DhSHdqa4=
=CHq3
-----END PGP SIGNATURE-----