<div class="gmail_quote">On Wed, Jun 24, 2009 at 4:31 AM, Vincent Ladeuil <<a href="mailto:v.ladeuil%2Blp@free.fr">v.ladeuil+lp@free.fr</a>> wrote: <snip> <div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> cert_file: /usr/lib/python2.6/dist-packages/bzrlib/tests/ssl_certs/server.crt I bet that file doesn't exist on your machine right (they don't on mine at least) ? So what we have here is : - a bug in the test server, it shouldn't fail to start *silently*. And the test setUp should just abort if the server can't be started. - packaging bug, these test can't be run without these files, they seems to be included in the tarball though, so I suspect they are lost at installation time, Now, if you create copy the content from the ssl_certs directory from the bzr sources, the tests should pass. Vincent </blockquote></div> You are exactly correct. I thought I would be clever and run create_ssls.py myself to create server and ca certs. That did not go so well... so maybe the tests are hard-coded to particular pre-generated certs. So I just copied the certs from the bzr sources as you suggested and voila! A 'bzr selftest test_http' runs to completeion (and passes). So you appear to be correct about both bugs. You figured out what was going on, so you get first right of refusal to write them up. If you prefer, I'll do the typing. Either way is great, so long as we make sure they get logged. Thanks! -M