Error in tests for Dovecot 2.4.0 aarch64
When attempting to build Dovecot 2.4.0 on the aarch64 platform, when running tests...
test-file-cache.c:268: Assert failed: file_cache_set_size(cache, 1024) == -1 Panic: file test-common.c: line 222 (test_expect_error_string_n_times): assertion failed: (expected_errors == 0) test-common.c:256: Assert failed: suppress == TRUE Error: Raw backtrace: #0 fatal_handler_real[0x7f73779dcca0] -> #1 default_fatal_handler[0x7f73779dcda0] -> #2 i_panic[0x7f73779766ec] -> #3 test_file_cache[0x7f7377997740] -> #4 main[0x7f7377977420] -> #5 __libc_start_call_main[0x4000008f4210] -> #6 __libc_start_main[0x4000008f42c0] -> #7 _start[0x7f7377977980]
Any ideas on this one?
Peter
You might need to upgrade pigeonhole first. I had test failures and gone away when upgraded pigeonhole first. Also, I had test failures as result of outdated bison binary, I used to have 3 and upgraded to 3.8 and everything worked just fine.
On 2025-02-07 07:48, Peter via dovecot wrote:
When attempting to build Dovecot 2.4.0 on the aarch64 platform, when running tests...
test-file-cache.c:268: Assert failed: file_cache_set_size(cache, 1024) == -1 Panic: file test-common.c: line 222 (test_expect_error_string_n_times): assertion failed: (expected_errors == 0) test-common.c:256: Assert failed: suppress == TRUE Error: Raw backtrace: #0 fatal_handler_real[0x7f73779dcca0] -> #1 default_fatal_handler[0x7f73779dcda0] -> #2 i_panic[0x7f73779766ec] -> #3 test_file_cache[0x7f7377997740] -> #4 main[0x7f7377977420] -> #5 __libc_start_call_main[0x4000008f4210] -> #6 __libc_start_main[0x4000008f42c0] -> #7 _start[0x7f7377977980]
Any ideas on this one?
Peter
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
On 8/02/25 02:03, hi--- via dovecot wrote:
You might need to upgrade pigeonhole first. I had test failures and gone away when upgraded pigeonhole first.
Pigeonhole hasn't even entered the picture yet. This failure is in Dovecot.
Also, I had test failures as result of outdated bison binary, I used to have 3 and upgraded to 3.8 and everything worked just fine.
Bison is 3.7.4 and is the stock Bison for EL9. That said, I am fairly confident that it's not bison because it builds just fine for the x86_64 arch which uses the exact same version of bison.
Peter
Aha, it sounds like a real bug then. Maybe you submit to bugs mailing list?
On 2025-02-10 07:22, Peter via dovecot wrote:
On 8/02/25 02:03, hi--- via dovecot wrote:
You might need to upgrade pigeonhole first. I had test failures and gone away when upgraded pigeonhole first.
Pigeonhole hasn't even entered the picture yet. This failure is in Dovecot.
Also, I had test failures as result of outdated bison binary, I used to have 3 and upgraded to 3.8 and everything worked just fine.
Bison is 3.7.4 and is the stock Bison for EL9. That said, I am fairly confident that it's not bison because it builds just fine for the x86_64 arch which uses the exact same version of bison.
Peter
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
On 10/02/25 22:41, Zakaria via dovecot wrote:
Aha, it sounds like a real bug then. Maybe you submit to bugs mailing list?
What bugs mailing list? According to https://www.dovecot.org/bugreport-mail/ bug reports should be sent to this list, which is exactly what I did.
Peter
Aha, I see. I didnt know this. I thought there was another mailing list for bugs š¤.
On 2025-02-11 01:07, Peter via dovecot wrote:
On 10/02/25 22:41, Zakaria via dovecot wrote:
Aha, it sounds like a real bug then. Maybe you submit to bugs mailing list?
What bugs mailing list? According to https://www.dovecot.org/bugreport-mail/ bug reports should be sent to this list, which is exactly what I did.
Peter
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
On 7. Feb 2025, at 9.48, Peter via dovecot <dovecot@dovecot.org> wrote:
When attempting to build Dovecot 2.4.0 on the aarch64 platform, when running tests...
test-file-cache.c:268: Assert failed: file_cache_set_size(cache, 1024) == -1
This test attempts to shrink allowed address space with setrlimit(RLIMIT_AS) and then use mmap() to allocate memory. For some reason that still succeeds. The test works in my Ubuntu 24.04 / aarch64 though. So not really sure how to debug it further myself. In any case it's most likely not a real problem.
On 11/02/25 21:20, Timo Sirainen via dovecot wrote:
On 7. Feb 2025, at 9.48, Peter via dovecot <dovecot@dovecot.org> wrote:
When attempting to build Dovecot 2.4.0 on the aarch64 platform, when running tests...
test-file-cache.c:268: Assert failed: file_cache_set_size(cache, 1024) == -1
This test attempts to shrink allowed address space with setrlimit(RLIMIT_AS) and then use mmap() to allocate memory. For some reason that still succeeds. The test works in my Ubuntu 24.04 / aarch64 though. So not really sure how to debug it further myself. In any case it's most likely not a real problem.
At a complete guess it could be a bug in a specific version of glibc (2.34) that only appears in aarch64. I agree that it's not likely a real problem and I can build with tests turned off easily enough but I always feel more comfortable if these issues can be fixed so if there's anything I can do to help further troubleshoot please let me know.
As an aside the actual build is being done in a aarch64 mock container running with qemu emulation on an x86_64 system running Rocky Linux 9 for both the host (x86_64) and container (aarch64) platforms. This is an RPM build using only a slightly modified version of the .src.rpm that you provide in the community repos for EL8 and which I'm using (the same sources) to build both el8 and 9. I'm sure all of that likely complicates troubleshooting and sometimes I'm amazed that it works as well as it does.
As a second aside I might try building it on my rpi4b instead and see if there's any difference.
Peter
participants (4)
-
hiļ¼ zakaria.website
-
Peter
-
Timo Sirainen
-
Zakaria