[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
continuous integration
From: |
Bruno Haible |
Subject: |
continuous integration |
Date: |
Mon, 30 Jan 2023 20:01:35 +0100 |
Jim Meyering wrote:
> > To catch such failures sooner, should I set up a continuous integration
> > that does a "make check" once every week? (I have such CIs already for
> > Gnulib, gettext, and a couple of other projects. It's cheap to maintain.)
>
> Yes, please. Thanks!
The 'sed' CI is operational now: https://gitlab.com/gnu-sed/ci-distcheck
If you want to co-maintain it with me, let me know your GitLab login name,
so that I can assign you the permissions.
While setting up this CI, I noticed two problems:
1) bootstrap.conf specifies that 'rsync' is needed. But rsync is not needed
any more by 'gnulib-tool' and by 'bootstrap' since 2018-10-07.
<https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=0ddd440d18af7bb10437642f12721d83092f0bea>
Suggestion: Remove the need for rsync. Patch attached.
2) I'm seeing a test suite failure
FAIL: testsuite/panic-tests.sh
because the CI is running as root (in a Docker container). You can
reproduce it as follows:
$ wget https://meyering.net/sed/sed-ss.tar.xz
$ tar xf sed-ss.tar.xz
$ cd sed-4.8.46-c9a1
$ sudo bash
# ./configure
# make
# make check
...
FAIL: testsuite/panic-tests.sh
...
# cat testsuite/panic-tests.log
--- exp-err-temp 2023-01-30 18:31:32.976065762 +0100
+++ err-temp 2023-01-30 18:31:32.976065762 +0100
@@ -1 +0,0 @@
-sed: couldn't open temporary file
FAIL testsuite/panic-tests.sh (exit status: 1)
0001-Don-t-require-rsync-as-a-prerequisite.-It-is-no-long.patch
Description: Text Data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- continuous integration,
Bruno Haible <=