From: Eric Bavier <bavier@cray.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Disable gnulib's test-lock test in packages?
Date: Tue, 7 Nov 2017 04:45:46 +0000 [thread overview]
Message-ID: <CY4PR11MB1718F6B9EAD570FF3DB72E46B7510@CY4PR11MB1718.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87y3nkpuvq.fsf@gnu.org>
Pushed in acc2dab7f2f50c9169d6388007c770878eae4a9c
Eric Bavier, Scientific Libraries, Cray Inc.
________________________________________
From: Ludovic Courtès <ludo@gnu.org>
Sent: Sunday, November 5, 2017 10:12
To: Eric Bavier
Cc: guix-devel@gnu.org
Subject: Re: Disable gnulib's test-lock test in packages?
Hi!
Eric Bavier <bavier@cray.com> skribis:
> I ran the gnulib lock tests with the be95b17ae commit and the tests passed, then with the commit directly before and they failed; so I'm fairly confident.
Great, thanks for testing.
> Attached is an updated patch, which remove the *-gnulib-multi-core patches and disables the test on two more packages (augeas and gsasl). I was able to build most of the packages on gnulib's "users" list (https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=users.txt;h=4ea176f2ef622b5c12843ba3d5aa35217c58502b;hb=HEAD) except for octave, because texlive-bin's luajit tests fail on this system.
OK.
> From 8e4988cf0da5bb170184a41822ff316e2e7f9c29 Mon Sep 17 00:00:00 2001
> From: Eric Bavier <bavier@cray.com>
> Date: Mon, 30 Oct 2017 11:23:46 -0500
> Subject: [PATCH] gnu: Disable gnulib's test-lock test in packages.
>
> * gnu/packages/base.scm (findutils)[source]: Disable test-lock.
> * gnu/packages/gettext.scm (gettext-minimal)[source]: Ditto.
> * gnu/packages/libidn.scm (libidn)[source]: Ditto.
> * gnu/packages/libunistring.scm (libunistring)[source]: Ditto.
> * gnu/packages/augeas.scm (augeas)[source]: Ditto.
> * gnu/packages/gsasl.scm (gsasl)[source]: Ditto.
> * gnu/packages/patches/findutils-gnulib-multi-core.patch,
> gnu/packages/patches/gettext-gnulib-multi-core.patch,
> gnu/packages/patches/gettext-multi-core.patch,
> gnu/packages/patches/libunistring-gnulib-multi-core.patch: Delete patches.
> * gnu/local.mk (DIST_PATCH_DATA): Remove them.
OK for ‘core-updates’!
Thank you,
Ludo’.
prev parent reply other threads:[~2017-11-07 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 21:16 Disable gnulib's test-lock test in packages? Eric Bavier
2017-10-29 15:39 ` Ludovic Courtès
2017-11-01 18:56 ` Eric Bavier
2017-11-05 16:12 ` Ludovic Courtès
2017-11-07 4:45 ` Eric Bavier [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CY4PR11MB1718F6B9EAD570FF3DB72E46B7510@CY4PR11MB1718.namprd11.prod.outlook.com \
--to=bavier@cray.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).