Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1268851
| From | "Michael Terry" <mike@mterry.name> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1117392: deja-dup: FTBFS: Ok: 50 Fail: 8 |
| Date | 2025-11-03 02:50 +0100 |
| Message-ID | <LMRRL-a2aI-1@gated-at.bofh.it> (permalink) |
| References | <LCASe-2YSH-7@gated-at.bofh.it> <LCASe-2YSH-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
I see inconsistent failures on the aarch64 CI builder upstream too. But I don't have easy access to an ARM and thought maybe it was unique to my CI. Looking at these logs more closely, I see a lot of warnings about using g_setenv after threads are created. That sounds like the sort of thing that might cause flaky, architecture-dependent failures. So I reorganized the tests a little to avoid it: https://gitlab.gnome.org/World/deja-dup/-/commit/f82d49984533dc73157ff8dc0038084a4174e8c1 I don't know if that fixes the failures, but maybe? I'd like to fix them too, I've just not been able to reproduce it myself.
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#1117392: deja-dup: FTBFS: Ok: 50 Fail: 8 Santiago Vila <sanvila@debian.org> - 2025-10-05 19:40 +0200 Bug#1117392: deja-dup: FTBFS: Ok: 50 Fail: 8 Jeremy Bicha <jeremy@bicha.net> - 2025-11-02 04:20 +0100 Bug#1117392: deja-dup: FTBFS: Ok: 50 Fail: 8 "Michael Terry" <mike@mterry.name> - 2025-11-03 02:50 +0100
csiph-web