From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org
Cc: Daniel Kiper <dkiper@net-space.pl>,
Glenn Washburn <development@efficientek.com>
Subject: [PATCH 0/5] Testing improvements
Date: Sat, 19 Dec 2020 04:14:35 -0600 [thread overview]
Message-ID: <cover.1608372033.git.development@efficientek.com> (raw)
I've been working on getting continuous integration working in gitlab where
testing is being done in an Ubuntu image. This patch series improves various
tests. I've ordered the patches starting with the least controversial patches.
The last two patches I suspect may have some deserve some attention.
Patch 4 allows the partmap_test to pass. I'm not sure why the number of the
device has changed from the setup this test was previously working on. I
suspect it could be either because I'm using a newer qemu or because I'm using
a new firmware/bios.
Patch 5 disables functional tests that have been failing for a long time, by
commenting them out. When someone gets around to fixing them, they can be
uncommented. But as it is, they've been failing for some time and people ignore
those failures. This isn't so nice with a continuous integration system that
largely expects tests to be passing, so it can detect when there are new
failures.
Glenn
Glenn Washburn (5):
tests: Exit with skipped exit code when test not performed
tests: Make sure LANG is set properly for iso9660_test
tests: Make setup errors in grub-fs-tester hard errors
tests: Fix partmap_test for arm*-efi, disk numbering has changed
tests: Comment failing functional tests until we can get them working
again
grub-core/tests/lib/functional_test.c | 6 +++---
tests/core_compress_test.in | 2 +-
tests/iso9660_test.in | 6 ++++++
tests/partmap_test.in | 2 +-
tests/pseries_test.in | 2 +-
tests/util/grub-fs-tester.in | 11 ++++++-----
6 files changed, 18 insertions(+), 11 deletions(-)
--
2.27.0
next reply other threads:[~2020-12-19 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 10:14 Glenn Washburn [this message]
2020-12-19 10:14 ` [PATCH 1/5] tests: Exit with skipped exit code when test not performed Glenn Washburn
2020-12-19 10:14 ` [PATCH 2/5] tests: Make sure LANG is set properly for iso9660_test Glenn Washburn
2020-12-19 10:14 ` [PATCH 3/5] tests: Make setup errors in grub-fs-tester hard errors Glenn Washburn
2020-12-19 10:14 ` [PATCH 4/5] tests: Fix partmap_test for arm*-efi, disk numbering has changed Glenn Washburn
2020-12-19 10:14 ` [PATCH 5/5] tests: Comment failing functional tests until we can get them working again Glenn Washburn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1608372033.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.