Running 

EXTRATESTOPTS='-x test_gdb -uall -v' make testall

Produces:

....
test_csv
test_ctypes
test test_ctypes produced unexpected output:
**********************************************************************
Trying:
    from ctypes import *
Expecting nothing
ok
Trying:
    array = (c_char_p * 5)()
Expecting nothing
ok
Trying:
    print array._objects
Expecting:
    None
ok
Trying:
    array[4] = 'foo bar'
Expecting nothing
ok
Trying:
    array._objects
Expecting:
    {'4': 'foo bar'}
ok
Trying:
    array[4]
Expecting:
    'foo bar'
ok
Trying:
    class X(Structure):
        _fields_ = [("x", c_int), ("y", c_int), ("array", c_char_p * 5)]
Expecting nothing
ok
Trying:
    x = X()
Expecting nothing
ok
Trying:
    print x._objects
Expecting:
    None
ok
Trying:
    print x.array._b_base_ # doctest: +ELLIPSIS
Expecting:
    <ctypes.test.test_objects.X object at 0x...>
ok
Trying:
    x.array[0] = 'spam spam spam'
Expecting nothing
ok
Trying:
    x._objects
Expecting:
    {'0:2': 'spam spam spam'}
ok
Trying:
    x.array._b_base_._objects
Expecting:
    {'0:2': 'spam spam spam'}
ok
2 items had no tests:
    ctypes.test.test_objects.TestCase
    ctypes.test.test_objects.TestCase.test
1 items passed all tests:
  13 tests in ctypes.test.test_objects
13 tests in 3 items.
13 passed and 0 failed.
Test passed.

**********************************************************************
test_curses
.....
test_zipimport
test test_zipimport produced unexpected output:
**********************************************************************
Trying:
    log.append(True)
Expecting nothing
ok
1 items passed all tests:
   1 tests in xyz.txt
1 tests in 1 items.
1 passed and 0 failed.
Test passed.
Trying:
    log.append(True)
Expecting nothing
ok
1 items passed all tests:
   1 tests in xyz.txt
1 tests in 1 items.
1 passed and 0 failed.
Test passed.

**********************************************************************
test_zipimport_support
test_zlib
366 tests OK.
4 tests failed:
    test_ctypes test_urllib2net test_urllibnet test_zipimport
26 tests skipped:
    test_aepack test_al test_applesingle test_bsddb test_bsddb185
    test_bsddb3 test_cd test_cl test_curses test_dl test_gl
    test_imageop test_imgfile test_kqueue test_linuxaudiodev
    test_macos test_macostools test_msilib test_ossaudiodev
    test_pep277 test_scriptpackages test_startfile test_sunaudiodev
    test_winreg test_winsound test_zipfile64
2 skips unexpected on linux2:
    test_bsddb test_bsddb3

Clearly the test_ctypes and the test_zipimport are not failing but the test suite thinks so. In fact, rerunning without the -v let them succeed.

Do you want to propose a patch?

Ok, let me dig into it and see if I can figure it out

On 04/20/2014 05:10 PM, Ezio Melotti wrote:
>
> Ezio Melotti added the comment:
>
> Do you want to propose a patch?
>
> ----------
> components: +Tests
> nosy: +ezio.melotti
> type:  -> behavior
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue21278>
> _______________________________________
>

This bug is extremely hard to reproduce in a controlled manner.
I mean, if I run

EXTRATESTOPTS='-x test_gdb -uall -v' make testall

it appears 100% of the times (whereas the same command without the -v 
works just fine, as I initially mentioned).

But I do not want to run the whole thing, so I resorted to

EXTRATESTOPTS='-uall -v -f ctypes_and_zipimport' make testall

where the ctypes_and_zipimport file contains test_ctypes,
test_zipimport and a handful of other tests. For all the tries I did, 
this always succeeded.

So I can't debug this issue, sorry.

Even running `EXTRATESTOPTS='-x test_gdb -uall -v' make testall` I can not reproduce this. I'll dig some more in the code for anything suspicious.

Ezio also couldn't reproduce this, so unless someone else (ddvento?), can reproduce it, I would advocate closing this issue.

As there has been no response can this be closed?

If no one is able to reproduce it, I guess we can close it.

I am sure I can reproduce it if I run it in the same situation I ran
it the first time. However, I initially reported the bug for python
2.7.6 i.e. two versions ago, so it might have been fixed by something
that happened meanwhile (or did the ones who tried used the exact
version I reported the bug against?)

If I experience the bug again while installing v2.7.9, I will report
it here again (you all receive updates even if the bug is closed,
right? I am asking because I don't thing I have the rights to re-open
it).

Thanks,
Davide

On Sat, Oct 4, 2014 at 6:47 PM, Mark Lawrence <report@bugs.python.org> wrote:
>
> Mark Lawrence added the comment:
>
> As there has been no response can this be closed?
>
> ----------
> nosy: +BreamoreBoy
> status: pending -> open
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue21278>
> _______________________________________

> If no one is able to reproduce it, I guess we can close it.

OK

> you all receive updates even if the bug is closed, right? 

Yes.