From: Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org>
To: Bruno Haible <bruno@clisp.org>
Cc: "Tim Rühsen" <tim.ruehsen@gmx.de>,
"Bernhard Voelker" <mail@bernhard-voelker.de>,
bug-gnulib@gnu.org
Subject: Re: gnulib-ci project
Date: Fri, 14 May 2021 22:36:53 +0200 [thread overview]
Message-ID: <87wns16oii.fsf@latte.josefsson.org> (raw)
In-Reply-To: <10394831.iFVxJUgNGh@omega> (Bruno Haible's message of "Fri, 14 May 2021 22:22:29 +0200")
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
Bruno Haible <bruno@clisp.org> writes:
> Simon Josefsson wrote:
>> Was anyone working on setting up CI/CD for gnulib on GitLab?
>> I recall there was a private project for it, but I don't have access.
>> Any reason for this? I have become rather aquinted with GitLab CI/CD
>> lately so it would be easy for me to setup something from scratch.
>
> There's no point in duplicating the effort already done, and creating
> confusion by having two different gnulib CIs on the same platform.
>
> https://gitlab.com/gnulib/gnulib-ci/-/pipelines
Great -- seems straightforward, although it would be nice to have it
passing a build before adding more platforms. It seems there are only
two tests that unexpectedly pass, the test-asyncsafe-linked_list-weak.sh
and test-asyncsafe-linked_list-strong.sh. Any ideas on these? I'm not
sure if they have already been discussed.
https://gitlab.com/gnulib/gnulib-ci/-/jobs/1246762022/artifacts/file/gnulib/testdir/gltests/test-asyncsafe-linked_list-strong.sh.log
> Tim,
>
> I have asked you twice [1][2] whether it's OK to make the project public.
I know Tim is busy on a new job so let's make him proud of what he
started by improving it :-)
/Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-05-14 20:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 23:06 replacement for 'join'? Bruno Haible
2021-04-05 22:48 ` Bernhard Voelker
2021-04-06 1:01 ` Bruno Haible
2021-04-06 2:24 ` Paul Eggert
2021-04-06 9:40 ` Bernhard Voelker
2021-04-06 18:47 ` Paul Eggert
2021-04-06 20:45 ` Bruno Haible
2021-04-07 12:04 ` Bernhard Voelker
2021-04-07 12:42 ` Bruno Haible
2021-05-12 10:01 ` Simon Josefsson via Gnulib discussion list
2021-05-12 10:39 ` Bruno Haible
2021-05-12 17:58 ` Simon Josefsson via Gnulib discussion list
2021-05-14 13:17 ` Bernhard Voelker
2021-05-14 13:42 ` Bruno Haible
2021-05-14 13:48 ` Simon Josefsson via Gnulib discussion list
2021-05-14 16:19 ` Bruno Haible
2021-05-14 17:15 ` Bernhard Voelker
2021-05-14 17:42 ` Simon Josefsson via Gnulib discussion list
2021-05-14 19:04 ` Bernhard Voelker
2021-05-14 20:22 ` gnulib-ci project Bruno Haible
2021-05-14 20:36 ` Simon Josefsson via Gnulib discussion list [this message]
2021-05-14 21:38 ` Bruno Haible
-- strict thread matches above, loose matches on Subject: below --
2020-09-06 0:52 [PATCH] verify: avoid __builtin_assume Paul Eggert
2020-09-20 14:57 ` Bruno Haible
2020-09-20 17:23 ` Jim Meyering
2020-09-20 19:07 ` gnulib-ci project Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wns16oii.fsf@latte.josefsson.org \
--to=bug-gnulib@gnu.org \
--cc=bruno@clisp.org \
--cc=mail@bernhard-voelker.de \
--cc=simon@josefsson.org \
--cc=tim.ruehsen@gmx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).