test_struct currently fails on the ARM buildbots;  see:

http://www.python.org/dev//buildbot/builders/ARMv4%20Debian%203.x/builds/275/steps/test/logs/stdio


======================================================================
FAIL: test_bool (test.test_struct.StructTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/pybot/buildarea-armeabi/3.x.klose-linux-armeabi/build/Lib/test/test_struct.py", line 521, in test_bool
    "ExplodingBool())" % (prefix + '?'))
AssertionError: Expected IOError: struct.pack('>?', ExplodingBool())

I don't really know where to start with this.  At the point of failure, struct.pack('<?', ExplodingBool()) has already been tested (and presumably raised the expected IOError).

Moreover, the struct module uses the same function, bp_bool, for packing with both '<?' and '>?', so it's a bit mystifying that one of these fails while the other passes.

The usage of char in bp_bool will not work if char is unsigned. Hopefully
that is the cause.

'sizeof y' is obviously wrong now in the memcpy. Next attempt.

Thanks, Stefan!  Fixed (I hope) in r82941 (py3k).

Now I'm puzzled about why the test passes for '<?'.  But let's see what the buildbots do.

Merged to release31-maint in r82942, release27-maint in r82945, release26-maint in r82946.

(And added missing Misc/NEWS entries for this change in r82943, r82944.)

> Now I'm puzzled about why the test passes for '<?'.

Somewhere along the way native_table is used instead of lilendian_table,
so np_bool is called.

> Somewhere along the way native_table is used instead of lilendian_table,
> so np_bool is called.

Hmm.  This doesn't alleviate my confusion. :)

The relevant part of test_struct looks like:

    for prefix in tuple("<>!=")+('',):
        # other tests
        try:
            struct.pack(prefix + '?', ExplodingBool())
        except IOError:
            pass
        else:
            self.fail("Expected IOError: struct.pack(%r, "
                      "ExplodingBool())" % (prefix + '?'))

So the '<?' test should happen directly before the '>?' test.  But the '<?' test was apparently passing, while the '>?' one was failing.  I don't see how native_table is relevant here, but am probably missing something.

On the other hand, with the pre-patch code, we end up with a method that sets a Python error but then returns a return value that indicates no error happened, and all sorts of unpredictable things can happen at that point...

Mark Dickinson <report@bugs.python.org> wrote:
> > Somewhere along the way native_table is used instead of lilendian_table,
> > so np_bool is called.
> 
> Hmm.  This doesn't alleviate my confusion. :)

I suppose I sounded a bit like the Oracle of Delphi here. :)

I compiled with OPT="-O0 -g -funsigned-char" and stepped through the code (pre-patch).
With '<', np_bool is substituted for bp_bool (apparently in PyInit__struct).

np_bool correctly returns -1, so the problem does not occur.

Ah yes; I missed that bit of PyInit__struct;  thank you!

Setting to pending; I'll close once the buildbots have reported back (it might take some days for the ARM buildbots to catch up).

Many thanks for the diagnosis.