Testing build

[Chris Angelico]

On Thu, May 14, 2015 at 1:18 AM, Cecil Westerhof <Cecil at decebal.nl> wrote:
> With:
>     python3 -m test -j3
> I now get:
>     Traceback (most recent call last):
>       File "/usr/lib64/python3.4/runpy.py", line 170, in _run_module_as_main
>         "__main__", mod_spec)
>       File "/usr/lib64/python3.4/runpy.py", line 85, in _run_code
>         exec(code, run_globals)
>       File "/usr/lib64/python3.4/_import_failed/test.py", line 21, in <module>
>         Please file a bug on the Novell Bugzilla.""")
>     ImportError: Module '{}' is not installed.
>     It is supposed to be part of python3 distribution, but missing from failed import map.
>     Please file a bug on the Novell Bugzilla.

... wat?

I'm having trouble parsing the grammar of that, but I'm guessing
something isn't properly set up to allow you to run the test suite on
Python 3. You could try using your package manager (is that zypper?)
to install more Python packages, though I'm not sure what you'd go
for. Is there a "python3-all" package, perhaps? Otherwise, try a
"python3-dev" package, or similar.

In any case, you shouldn't have this problem on a Py3 that you build
from source. What you're looking at is a cut-down Python standard
library that assumes that most people won't need to run the test suite
- which is a reasonable assumption, but one you're now breaking. :)

> With:
>     python2 -m  test.regrtest -j3
> I now get:
>     354 tests OK.
>     3 tests failed:
>         test_distutils test_gdb test_poplib
>     4 skips unexpected on linux2:
>         test_dbm test_gdbm test_idle test_tools
>
> This is on openSUSE 13.2.

This looks like a normal test run. You're seeing some failures, which
should have been run verbosely further above; the unexpected skips
might mean that you need to tell the test runner that it's allowed to
use certain resources, but otherwise they're probably not a big deal.

ChrisA