[Top][All Lists]

[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:

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.

Suggestion: Remove the need for rsync. Patch attached.

2) I'm seeing a test suite failure
FAIL: testsuite/
because the CI is running as root (in a Docker container). You can
reproduce it as follows:

$ wget
$ tar xf sed-ss.tar.xz
$ cd sed-4.8.46-c9a1
$ sudo bash
# ./configure
# make
# make check
FAIL: testsuite/
# 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/ (exit status: 1)

Attachment: 0001-Don-t-require-rsync-as-a-prerequisite.-It-is-no-long.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]