Testing build

[Cecil Westerhof]

Op Wednesday 13 May 2015 16:12 CEST schreef Chris Angelico:

> On Wed, May 13, 2015 at 11:53 PM, Cecil Westerhof <Cecil at decebal.nl> wrote:
>> To be clear I did not built Python yet, I used the versions
>> installed on my system. (3.4.1 and 2.78)
>>
>> After looking at:
>> https://docs.python.org/devguide/
>>
>> I executed first:
>> python3 -m test -j3
>> which gave:
>> a1: [6.435562750993995, 6.446765303000575, 6.405053696988034]
>> a2: [4.437405036995187, 4.101042214999325, 4.112324360001367]
>> a3: [4.096015618008096, 4.123215412007994, 4.108890180999879]
>> [1, 5, 6, 9, 11, 13, 19, 20, 28, 30, 34, 38, 39, 40, 42, 49, 52,
>> 53, 57, 58, 62, 63, 66, 68, 72, 73, 74, 76, 78, 82, 83, 85, 86, 88,
>> 96, 98, 102, 105, 109, 110, 114, 118, 121]
>> [1, 5, 6, 9, 11, 13, 19, 20, 28, 30, 34, 38, 39, 40, 42, 49, 52,
>> 53, 57, 58, 62, 63, 66, 68, 72, 73, 74, 76, 78, 82, 83, 85, 86, 88,
>> 96, 98, 102, 105, 109, 110, 114, 118, 121]
>> [1, 5, 6, 9, 11, 13, 19, 20, 28, 30, 34, 38, 39, 40, 42, 49, 52,
>> 53, 57, 58, 62, 63, 66, 68, 72, 73, 74, 76, 78, 82, 83, 85, 86, 88,
>> 96, 98, 102, 105, 109, 110, 114, 118, 121]
>>
>> What is the meaning of this?
>
> Do you have a directory named 'test' or a file named 'test.py' in
> the current directory? If so, it'll be loading that up instead of
> the standard library 'test' module.

Oops, that was the problem. Moved and problem solved.

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.

With:
    python2 -m  test.regrtest -j3
I now get:
    .
    .
    .
    test_xpickle -- skipping backwards compat tests.
    Use 'regrtest.py -u xpickle' to run them.
    test_wait4
    test_xrange
    test_zipfile64
    test_zipfile64 skipped -- test requires loads of disk-space bytes and a long time to run
    test_zipimport
    test_xmlrpc
    test_zipimport_support
    test_zlib
    test_zipfile
    354 tests OK.
    3 tests failed:
        test_distutils test_gdb test_poplib
    1 test altered the execution environment:
        test_site
    41 tests skipped:
        test_aepack test_al test_applesingle test_bsddb185 test_bsddb3
        test_cd test_cl test_codecmaps_cn test_codecmaps_hk
        test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_curses
        test_dbm test_dl test_gdbm test_gl test_idle test_imageop
        test_imgfile test_kqueue test_linuxaudiodev test_macos
        test_macostools test_msilib test_ossaudiodev test_py3kwarn
        test_scriptpackages test_smtpnet test_socketserver test_startfile
        test_sunaudiodev test_timeout test_tk test_tools test_ttk_guionly
        test_urllib2net test_urllibnet test_winreg test_winsound
        test_zipfile64
    4 skips unexpected on linux2:
        test_dbm test_gdbm test_idle test_tools

This is on openSUSE 13.2.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof