Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #90549 > unrolled thread

Testing build

Back to article view | Back to comp.lang.python

Contents

  Testing build Cecil Westerhof <Cecil@decebal.nl> - 2015-05-13 15:53 +0200
    Re: Testing build Chris Angelico <rosuav@gmail.com> - 2015-05-14 00:12 +1000
      Re: Testing build Cecil Westerhof <Cecil@decebal.nl> - 2015-05-13 17:18 +0200
        Re: Testing build Chris Angelico <rosuav@gmail.com> - 2015-05-14 01:45 +1000
          Re: Testing build Cecil Westerhof <Cecil@decebal.nl> - 2015-05-13 19:15 +0200

#90549 — Testing build

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?

After this I executed:
    python2 -m  test.regrtest -j3
which gave:
    a1: [3.996155023574829, 3.9603538513183594, 3.9782469272613525]
    a2: [4.345172166824341, 4.30767297744751, 4.409227132797241]
    a3: [4.328500032424927, 4.3080408573150635, 4.324347019195557]
    [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]
    /usr/bin/python2: No module named test.regrtest

What is happening here?

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

[toc] | [next] | [standalone]

#90551

On Wed, May 13, 2015 at 11:53 PM, Cecil Westerhof <Cecil@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.

ChrisA

[toc] | [prev] | [next] | [standalone]

#90564

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

> On Wed, May 13, 2015 at 11:53 PM, Cecil Westerhof <Cecil@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

[toc] | [prev] | [next] | [standalone]

#90565

On Thu, May 14, 2015 at 1:18 AM, Cecil Westerhof <Cecil@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

[toc] | [prev] | [next] | [standalone]

#90572

Op Wednesday 13 May 2015 17:45 CEST schreef Chris Angelico:

> On Thu, May 14, 2015 at 1:18 AM, Cecil Westerhof <Cecil@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.

I needed python3-testsuite. For python 3 that is needed, for python 2
not.

Now I get:
    .
    .
    .
    [381/388/4] test_xmlrpc_net
    test_xmlrpc_net skipped -- Use of the 'network' resource not enabled
    [382/388/4] test_wait4
    [383/388/4] test_zipfile64
    test_zipfile64 skipped -- test requires loads of disk-space bytes and a long time to run
    [384/388/4] test_zipimport
    [385/388/4] test_zipimport_support
    [386/388/4] test_zlib
    [387/388/4] test_xmlrpc
    [388/388/4] test_zipfile
    355 tests OK.
    4 tests failed:
        test_compileall test_dbm_dumb test_pydoc test_site
    29 tests skipped:
        test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp
        test_codecmaps_kr test_codecmaps_tw test_curses test_dbm
        test_dbm_gnu test_dbm_ndbm test_devpoll test_gdb test_idle
        test_kqueue test_msilib test_ossaudiodev test_shelve test_smtpnet
        test_socketserver test_startfile test_timeout test_tk test_tools
        test_ttk_guionly test_urllib2net test_urllibnet test_winreg
        test_winsound test_xmlrpc_net test_zipfile64

I will look into it later, but it does not look to bad.


> 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. :)

Sometimes I do things a little differently. ;-)

>> 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.

I will look into this also later.

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

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web