Test failure on ARM: backtrace_append

Julien Lepiller
Thu, 20 Feb 2020 18:31:26 -0000

Le 20 f?vrier 2020 12:58:52 GMT-05:00, Aki Tuomi <aki.tuomi at
open-xchange.com> a ?crit :
>
>> On 20/02/2020 18:56 Julien Lepiller <julien at lepiller.eu>
wrote:
>>
>>
>> Hi,
>>
>> I am a packager in Guix and user of dovecot on an ARM server (armhf).
>The Guix package fails to build because of a test error (see the last
>lines of the full build log:
>https://ci.guix.gnu.org/log/f5if2qb5rsqag3a6jy5vga1l9hm9pkj0-dovecot-2.3.9.3).
>As the name suggests, this is dovecot 2.3.9.3, the latest version.
>Previous versions built fine, as well as the same version on x86 and
>x86_64. Note that the build on guix's build farm was done in a qemu vm,
>but I got the same test failure on real hardware.
>>
>> I'm not sure what the best course of action is. Did I find a
>legitimate bug, or should I simply ignore that test for that
>architecture? Dovecot itself seems to be running fine when I ignore the
>tests.
>>
>> Thanks for any guidance you could provide!
>
>(sorry for the previous mail, client acted up...)
>
>Can you provide backtrace for the core file? This seems to be related
>to libunwind somehow.
>
>Aki

I can try, but it will take me some time to rebuild. I forgot to keep the
previous attempts. I think this is unrelated to libunwind since the asserts that
fail are in the #elif case for libunwind. We don't build with libunwind
(should we? What does it bring us?)