From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B1012C3A5A1 for ; Thu, 22 Aug 2019 16:52:15 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 88B72233FC for ; Thu, 22 Aug 2019 16:52:15 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 88B72233FC Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:45950 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i0qJq-0000j9-Ph for qemu-devel@archiver.kernel.org; Thu, 22 Aug 2019 12:52:14 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:51665) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i0qIa-0008T1-SB for qemu-devel@nongnu.org; Thu, 22 Aug 2019 12:50:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i0qIZ-0007XG-Tp for qemu-devel@nongnu.org; Thu, 22 Aug 2019 12:50:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58160) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i0qIZ-0007Wj-OY for qemu-devel@nongnu.org; Thu, 22 Aug 2019 12:50:55 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 15C33C049D59; Thu, 22 Aug 2019 16:50:55 +0000 (UTC) Received: from work-vm (ovpn-117-231.ams2.redhat.com [10.36.117.231]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9C7AA60603; Thu, 22 Aug 2019 16:50:47 +0000 (UTC) Date: Thu, 22 Aug 2019 17:50:45 +0100 From: "Dr. David Alan Gilbert" To: Paolo Bonzini Message-ID: <20190822165045.GM3277@work-vm> References: <20190822114747.GS3267@redhat.com> <20190822163150.GA3332@work-vm> <9caf3a64-0841-dde6-3413-a77dc80e22bd@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9caf3a64-0841-dde6-3413-a77dc80e22bd@redhat.com> User-Agent: Mutt/1.12.1 (2019-06-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Thu, 22 Aug 2019 16:50:55 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.132.183.28 Subject: Re: [Qemu-devel] more automated/public CI for QEMU pullreqs X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peter Maydell , Daniel =?iso-8859-1?Q?P=2E_Berrang=E9?= , Samuel Ortiz , Kashyap Chamarthy , Philippe =?iso-8859-1?Q?Mathieu-Daud=E9?= , Richard Henderson , QEMU Developers , Stefan Hajnoczi , Alex =?iso-8859-1?Q?Benn=E9e?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" * Paolo Bonzini (pbonzini@redhat.com) wrote: > On 22/08/19 18:31, Dr. David Alan Gilbert wrote: > >> With both these points in mind, I think it is pretty hard sell to > >> say we should write & maintain a custom CI system just for QEMU > >> unless it is offering major compelling functionality we can't do > >> without. (That was Dan's comment) > In theory I agree. > > In practice, the major compelling functionality is portability. If it > is true that setting up runners is problematic even on aarch64, frankly > GitLab CI is dead on arrival. If it is not true, then I'd be very happy > to use GitLab CI too. IMHO if for some weird reason Gitlab has problems on aarch64 then we just need to get that fixed. Dave > Paolo > > > I'd agree; and I'd also find it useful to have runners setup for > > Gitlab CI for related things (it would be useful for the virtio-fs > > stuff); if there are problems on other architectures then we should > > find some go wranglers to go fix it. -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK