[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#64711] [PATCH 00/45] Fix builds and skip failing tests for the Hurd
From: |
Janneke Nieuwenhuizen |
Subject: |
[bug#64711] [PATCH 00/45] Fix builds and skip failing tests for the Hurd. |
Date: |
Tue, 18 Jul 2023 22:23:00 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
Ludovic Courtès writes:
Hi!
> Great work!
Thank yout!
> A general comment: these changes to test suites were made based on
> feedback from non-chrooted builds, whose outcome is influenced by system
> state such as running translators. Until we have chroot builds, I think
> we should be cautious and not invest too much time.
That's a helpful perspective, thanks for sharing.
[snip coreutil's long list of failing patches]
> For example, I wonder how reliable this long list is. Some of these
> tests may fiddle with /proc, /etc/fstab, and other things not under
> control, which means some might suddenly pass for some reason. So I
> wonder if we should just #:tests? #f in this case.
>
> Thoughts?
In this case, having invested the time to identify hanging and failing
tests, I would suggent to keep the list; but I'm also fine with using
#:tests? #f when more than, say 15 tests fail?
What I failed to mention, is that I looked into what Debian is doing for
cases like these, and without exception they just skip the test suite
for the Hurd, even for critical packages such as coreutils and python.
>
> (With other, higher-level test suites with a couple of failures, it’s
> probably still a good idea to skip individual tests instead of the whole
> test suite.)
Noted. Now I'm wondering whether glib should be considered to have
higher level tests. It would have been nice if I kept some kind of
record on this. It will be a bit less painful te re-check once CI built
most upto glib, dunno.
Greetings,
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
- [bug#64711] [PATCH 05/43] Revert "gnu: sed: Skip failing test on GNU/Hurd.", (continued)
- [bug#64711] [PATCH 05/43] Revert "gnu: sed: Skip failing test on GNU/Hurd.", Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 01/43] Revert "gnu: libunistring: Fix make check for the Hurd.", Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 02/43] gnu: guile: Skip hanging and failing pipe tests on the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 04/43] gnu: grep: Update hanging and failing tests on the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 03/43] gnu: coreutils: Skip hanging and failing test on the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 06/43] gnu: findutils: Move test-strerror_r from XFAIL to skip on the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 07/43] gnu: diffutils: Remove test-perror2 from XFAIL_TESTS on the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 09/43] gnu: m4: Skip gnulib stack-overflow tests for the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 14/43] gnu: libbsd: Skip failing test on the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 15/43] gnu: c-ares: Skip failing tests on the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 13/43] gnu: elfutils: Skip failing tests on the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 08/43] gnu: gettext-minimal: Remove XFAIL_TESTS for the Hurd., Janneke Nieuwenhuizen, 2023/07/18
- [bug#64711] [PATCH 10/43] gnu: openssl: Build fix for the Hurd., Janneke Nieuwenhuizen, 2023/07/18