From owner-freebsd-hackers@freebsd.org Fri Aug 30 17:42:32 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3B925D4672 for ; Fri, 30 Aug 2019 17:42:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Kmyb36YNz4MKc for ; Fri, 30 Aug 2019 17:42:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x734.google.com with SMTP id f10so6866209qkg.7 for ; Fri, 30 Aug 2019 10:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mEDmYyGD+aYCJIMJYKGfdtezYOt6DpNDj2A2wQiDr08=; b=VUzHJ6gChxj7MjPGyoI5/keny6o1rjNfuJHVGRmcrGI0hYpSo4b23PWanSGJHUDYhR /IpvuKffI5ofRjssqynombCtRpQanlYw5kT3tWUny5XnlQySBBy7rI+4CisHmVPnouN0 J51YyROOu5TuulfIBZ350CJGWTROspnalzGsKnluCavCkWS17UQDX1dnzv3V8I4I3Tm2 VVm3UYx7KnhEEcc8e+l9aqOax3G9xNWdyEd4yUVxqfEBPukCY1DnQ4GYLTUo3AiPpauG EjAMoXooXgiiANRSb4wLoY6/IiEt7sCx/7IEP4y2mnuYEgleDkBObIg0NiNdC7qRQZjy Hq5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mEDmYyGD+aYCJIMJYKGfdtezYOt6DpNDj2A2wQiDr08=; b=JKOtlq0eaf54kSGM91XTs9QMKyY+//wTKTjn9DlpP/oW3yQB8ZlFDSj3e0vomlTudB Y+usFtktuLs+r/ze02trAh6TkWOe6TPLprwyGgDcaLCfAnhK1ahPToR7PD9C+iU/hNtH OLt/6lQMgR/0kMYWbijSAOPL1Z45poQETdVUtrKJ7VlFs9EW9uYcN40/yrXhGMaEXydl qDzKVm7ftuINZEr7t1ZwbOoGjLl7xJywhcgu6F44nNMY5lbPcS4SOa7kH2c4XKmPmn+u rdfMCGXvA9xIa1oA7S2hDDtnSe1eiziD8ESRUsvKlqnPb7y4jmsGeg/js/gUnUTG+iS3 Zdaw== X-Gm-Message-State: APjAAAX9ZdCNwoyZpKDVCwjHzK9q173N5MhHspQKx7U3evcBAaST+CIk uzp5Q3ZJ/UNg199eiejIxqlOYJzcJ2lvQ0w2NZGbpkKZD7g= X-Google-Smtp-Source: APXvYqx2MNSmSeQi3YG5eOV6OO7gtnz8xJKpvOafPnEie0JxjyLF+yTqI3YbtFyr3vqifFE5iFvwr+tVqTyprh1YGOY= X-Received: by 2002:a37:4804:: with SMTP id v4mr17147516qka.60.1567186950326; Fri, 30 Aug 2019 10:42:30 -0700 (PDT) MIME-Version: 1.0 References: <339B7A20-F88D-4F60-B133-612189663272@gmail.com> In-Reply-To: <339B7A20-F88D-4F60-B133-612189663272@gmail.com> From: Warner Losh Date: Fri, 30 Aug 2019 11:42:19 -0600 Message-ID: Subject: Re: FCP 20190401-ci_policy: CI policy To: Enji Cooper Cc: Li-Wen Hsu , FreeBSD Hackers , fcp@freebsd.org X-Rspamd-Queue-Id: 46Kmyb36YNz4MKc X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=VUzHJ6gC; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::734) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-5.92 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-0.996,0]; RCVD_IN_DNSWL_NONE(0.00)[4.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.92)[ip: (-9.41), ipnet: 2607:f8b0::/32(-2.84), asn: 15169(-2.32), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 17:42:32 -0000 On Fri, Aug 30, 2019 at 10:25 AM Enji Cooper wrote: > > Taking a step back, as others have brought up, we=E2=80=99re currently hi= ndered by > tooling: we are applying a DVCS (git, hg) based technique (CI) to > subversion and testing changes after they=E2=80=99ve hit head, instead of= before > they hit head. > > While phabricator can partially solve this by testing upfront (we don=E2= =80=99t > enforce this; I=E2=80=99ve made my concerns with this not being a require= ment > well-known in the past), the solution is limited by bandwidth for testing= , > i.e., testing is an all or nothing exercise right now and building multip= le > toolchains/architectures takes a considerable amount of time. We could > leverage cloud/distributed solutions for this (Cirrus CI, Travis if the > integration existed), but this would require using github or teaching a > tool how to make the appropriate REST api calls to run the tests and quer= y > the status (in progress, pass, fail, etc). > > Applying labels and filtering on test suites will get us partway to a > final solution from a test perspective, but a lot of work needs to be don= e > with phabricator, etc. > > We also need to have build failures with tier 1 architectures with GENERI= C > be a commit blocking operation. Full stop. > Until we have a DCVS, this is a non-starter. It's too hard with svn. Let's table it until we have the migration to git complete. Also FreeBSD is huge, having to wait for a full build on all Tier-1 platforms also is a non-starter. It takes too long, and there's too many ways to build FreeBSD. Having a sanity check incremental build may be OK, but there's a number of changes that break the incremental -DNO_CLEAN build that are none-the-less fine for a complete rebuild. There's a ton of details to get right here to make it not an absolute nightmare for developers to get patches in and slow the velocity of changes to a crawl. Since we know nothing of our future git overlords, it's premature to even start this discussion because so many things dovetail with that effort we won't get beyond the basics (which people generally agree in principle on, but have concerns about the details that will be filibustered to death in the absence of a concrete git system it will add-on to). tl;dr: Love the concept, the devil is in the details to ensure we don't stifle momentum. Warner