testsuite fails with "warning: some compiled extensions could not be loaded"

[Christian Faulhammer]

Some tests in bzr 2.6.0 fail, because a warning sneaks into the output and leads to a string mismatch when comparing. As this is for Gentoo ebuilds (I am the maintainer), setting ignore_missing_extensions=True is not an option. Can I set this variable in the environment?

[19780] 2013-08-10 13:13:40.925 WARNING: bzr: warning: some compiled extensions could not be loaded; see <https://answers.launchpad.net/bzr/+faq/703>
}}}

Traceback (most recent call last):
  File "/var/tmp/portage/dev-vcs/bzr-2.6.0/work/bzr-2.6.0/bzrlib/tests/blackbox/test_serve.py", line 245, in test_bzr_serve_port_readwrite
    self.assertServerFinishesCleanly(process)
  File "/var/tmp/portage/dev-vcs/bzr-2.6.0/work/bzr-2.6.0/bzrlib/tests/blackbox/test_serve.py", line 151, in assertServerFinishesCleanly
    self.assertEqual('bzr: interrupted\n', result[1])
AssertionError: not equal:
a = 'bzr: interrupted\n'
b = 'bzr: interrupted\nbzr: warning: some compiled extensions could not be loaded; see <https://answers.launchpad.net/bzr/+faq/703>\n'

[John A Meinel (jameinel)]

Is there a reason you aren't building the extensions before running the test suite?

The extensions are *highly* recommended in a final bzr install.

[Vincent Ladeuil (vila)]

Some tests are *not* meant to be run without the compiled extensions.

The blackbox ones are more sensible to the kind of failure you're seeing because they often rely on a precise output.

While bzr *can* be used without the compiled extensions, there are specific tests to verify that with and without using the extensions.