From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Patchwork + automated checking and testing of patches Date: Thu, 22 Nov 2018 10:07:14 +0100 Message-ID: <87d0qxeb0d.fsf@gnu.org> References: <87h8h29z2j.fsf@cbaines.net> <87in0ssw1r.fsf@cbaines.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42203) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gPkxC-0004sm-Ld for guix-devel@gnu.org; Thu, 22 Nov 2018 04:07:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gPkxB-0002kC-K5 for guix-devel@gnu.org; Thu, 22 Nov 2018 04:07:18 -0500 In-Reply-To: <87in0ssw1r.fsf@cbaines.net> (Christopher Baines's message of "Mon, 19 Nov 2018 19:32:16 +0000") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Christopher Baines Cc: Guix-devel Hi! Christopher Baines skribis: > This is still very much a prototype, but I think it's nearing the point > where it actually might be doing something useful. > > Currently, taking the service running the FreeDesktop fork of Patchwork, > you can go to the series page [10], and it will show you a list of patch > series, along with a indication of the "tests" status, which currently > is just whether the patch applied successfully to the master branch. > > 10: https://patchwork-fdo.cbaines.net/project/guix-patches/series/ The test part is nice! > The Patchwork service running the upstream code is very similar, you > just have to click in to the individual patches to get the information > on the "Checks", for an example, have a look at [11] > > 11: https://patchwork.cbaines.net/patch/233/ Neat. > Next, I'm planning to work on extending the test series job to actually > start running some code, maybe perhaps just applying the patch, and then > running make at first. Then maybe trying to use the (guix inferior) > module code to intelligently determine changed packages that need > building. If you have something that does this, or want to write > something to do this, that would be awesome. For this I would suggest building the code using (guix self). You can do that either in Scheme using =E2=80=98inferior-for-channels=E2=80=99 or w= ith something like: guix pull --url=3Dfile://=E2=80=A6 -p ./test-guix As for determining the list of new and upgraded packages, see =E2=80=98display-new/upgraded-packages=E2=80=99 in (guix scripts pull). We= can separate the computational part from the UI part in there. Perhaps we could integrate the tests with Mumi as well. Thanks for the great work! Ludo=E2=80=99.