On 02/01/2018 11:59 AM, Max Reitz wrote: >>> Hmmmm, now this fails again on my 32 bit build. :-( >>> >>> The issue there is that you get a "Cannot allocate memory" when trying >>> to open the file. My current fix was 2291712c39111a732 which simply >>> converted that to "Invalid argument", but now it's getting a bit more >>> complicated... Should I just continue to play the game and check the >>> output for "Cannot allocate memory" and print exactly what the reference >>> output is expecting...? >> >> Ahhh. OK, then, with a big comment. >> >> I'd say let's just _notrun on 32 bit. > > Sounds OK, but how would we test that? uname? Or just _notrun when we > see the ENOMEM message?
_notrun when you detect ENOMEM seems reasonable (the equivalent of exit status 77 in skipping a test in an automake context) -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
