Your message dated Mon, 15 Sep 2025 19:28:33 -0400
with message-id
<caaajcmassj9defq4bxasriyvghzx4ulzicqkxxv7e19h74p...@mail.gmail.com>
and subject line Re: nautilus FTBFS on riscv64
has caused the Debian Bug report #1114795,
regarding nautilus FTBFS on riscv64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1114795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114795
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: nautilus
Version: 49~rc-2
Severity: serious
Tags: ftbfs patch
X-Debbugs-Cc: [email protected]
User: [email protected]
Usertags: riscv64
https://buildd.debian.org/status/fetch.php?pkg=nautilus&arch=riscv64&ver=49~rc-2&stamp=1757359443&raw=0
...
ERROR:../test/automated/displayless/test-file-operations-archive.c:238:test_archive_file_long:
'data.success' should be TRUE
...
Summary of Failures:
7/21 nautilus:displayless / test-file-operations-archive
TIMEOUT 480.07s killed by signal 15 SIGTERM
Ok: 19
Fail: 0
Skipped: 1
Timeout: 1
dh_auto_test: error: cd obj-riscv64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb
LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --verbose returned exit code 1
make[1]: *** [debian/rules:42: override_dh_auto_test] Error 25
A fix is attached.
Description: Increase the test iterations to fix a FTBFS on riscv64
Author: Adrian Bunk <[email protected]>
--- nautilus-49~rc.orig/test/automated/test-utilities.h
+++ nautilus-49~rc/test/automated/test-utilities.h
@@ -4,7 +4,7 @@
#pragma once
-#define MAX_CONTEXT_ITERATIONS 1000
+#define MAX_CONTEXT_ITERATIONS 10000
#define ITER_CONTEXT_WHILE(CONDITION) \
for (guint context_iter = 0; \
--- End Message ---
--- Begin Message ---
Version: 49.0-1
Thank you for the suggested fix which upstream applied in today's 49.0
release and I confirm that it's working.
I rebased my git commits and my change that added this bug number to
the debian/changelog and credited you was accidentally removed.
Jeremy Bícha
--- End Message ---
