Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHBvl-0004Db-HD for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Jul 2022 22:24:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oHBuk-00034P-H1 for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Jul 2022 22:23:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oHBuk-0002zj-3n for pgsql-hackers@lists.postgresql.org; Thu, 28 Jul 2022 22:23:30 +0000 Received: from mail-il1-x135.google.com ([2607:f8b0:4864:20::135]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oHBuc-0008MG-7O for pgsql-hackers@lists.postgresql.org; Thu, 28 Jul 2022 22:23:28 +0000 Received: by mail-il1-x135.google.com with SMTP id y13so1636118ilv.5 for ; Thu, 28 Jul 2022 15:23:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc; bh=cwjH9/nGvlEE2CplcotFAOrbFFKEwxNw73H4v0E8nCY=; b=Ts9rLI5zP1MjlYLlTap2jm1FqADcNIWiGODYrnqwftmn1h3k6TARNIQmXFLUjLKYqP UG8c+UhxERYICyCsGUi5wqZKCvG2Z5Q7eX6/tymEbAgEkIprZQtSd6WtBApcUvjP1+G0 4Bg2iTYYkVG8PmizGVHkN36o0oVJzzoUadfm7qQ8D00eDV+UQwtpZPWcqDG8ZI4USsly r6UIQwTcyFIJXEo+1JcHYGCoRpskHAsuny7p8ArowIpbzOnA9n4sWIPcWkDFqvgE1Etr qSIRVJW2e9MTlehqYG6w2bK4ru7gt8srLAVoxi+9wm0ZPz+fc5Y+QToESZjB10zmYkdR 7LaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=cwjH9/nGvlEE2CplcotFAOrbFFKEwxNw73H4v0E8nCY=; b=Vqnrc5quT4orkj96EblU8IQH3wPd1rSjOaQu9r6Kxa+F6G2g9CuQ32B89VnMlmn/fG qiy0jI/xvfk83JX7UjkCSAEnzG/ZzeasGANjj44pER73Rlhdr/Co/VV/+VtAlNApWgho gMz9PInoeP39vnWt0LbhljSilz17/Ax8dx35oeVrKVo0qUqLZu/UDKIhCbdm4gU6ve8E y6orHNliLvFpycIpBO4bDJTSLYx/dWZZJANhjqI5BZs7EaI917AKqlYagNBsurKZEz3V GYseBaU8JvdsO4e2G7qm9im5CfRFce6ahIt1Yf7gXmvxrvtAYKiseyRmGSTMWu4ZAZVA FmKA== X-Gm-Message-State: AJIora+apVvspHP8e9Ba4h7SpZE4jOj32+ZvjR45ss0TMv5Ddvjcz4JU +bmB9rnihTBr7+CiDBCLRMzDaQ== X-Google-Smtp-Source: AGRyM1tpWHAo8MHXsx9f/FpTvZn9dUTwPLPE8b+oXLz80y/O8G28t9K1An2C2bdVvPZzbXBwh3bv8A== X-Received: by 2002:a92:c56a:0:b0:2dd:8248:1eab with SMTP id b10-20020a92c56a000000b002dd82481eabmr288033ilj.27.1659047001150; Thu, 28 Jul 2022 15:23:21 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id c40-20020a02962b000000b0034161ed8fadsm871830jai.150.2022.07.28.15.23.20 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Jul 2022 15:23:20 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id EB03980086E; Thu, 28 Jul 2022 17:23:19 -0500 (CDT) Date: Thu, 28 Jul 2022 17:23:19 -0500 From: Justin Pryzby To: Thomas Munro Cc: pgsql-hackers@lists.postgresql.org, Andrew Dunstan , Tom Lane Subject: Re: Cygwin cleanup Message-ID: <20220728222319.GL15006@telsasoft.com> References: <20220727064425.GG15006@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jul 29, 2022 at 10:04:04AM +1200, Thomas Munro wrote: > Thanks for working on this! > > Huh, that Cygwin being shipped by Choco is quite old, older than > lorikeet's, but not old enough to not have the bug: > > [04:33:55.234] Starting cygwin install, version 2.918 Hm, I think that's the version of "cygwinsetup" but not cygwin.. It also says this: [13:16:36.014] Cygwin v3.3.4.20220408 [Approved] > I wonder if you can tell Choco > to install an ancient version, but even if that's possible you'd be > dealing with other stupid problems and bugs. Yes: choco install -y --no-progress --version 4.6.1 ccache > > > XXX This should use a canned Docker image with all the right packages > > > installed > > > > Has anyone tried using non-canned images ? It sounds like this could reduce > > the 4min startup time for windows. > > > > https://cirrus-ci.org/guide/docker-builder-vm/#dockerfile-as-a-ci-environment > > Yeah, I had that working once. Not sure what the pros and cons would be for us. I think it could be a lot faster to start, since cirrus caches the generated docker image locally. Rather than (I gather) pulling the image every time. > > > XXX We would never want this to run by default in CI, but it'd be nice > > > to be able to ask for it with ci-os-only! (See commented out line) > > > only_if: $CIRRUS_CHANGE_MESSAGE =~ '.*\nci-os-only:[^\n]*cygwin.*' > > > > Doesn't this already do what's needed? > > As long as it doesn't also check: CHANGE_MESSAGE !~ 'ci-os-only', > > the task will runs only on request. > > Yeah I was just trying to say that I was sharing the script in a way > that always runs, but for commit we'd want that. This is all far too > slow for cfbot to have to deal with on every build. It occurred to me today that if cfbot preserved the original patch series, and commit messages, that would allow patch authors to write things like "ci-os-only: docs" for a doc only patch. I've never gotten cirrus' changesOnly() stuff to work... > Looks like we can expect to be able to build and test fast on Windows > soonish, though, Do you mean with meson ? > so maybe one day we'd just turn Cygwin and MSYS on? I didn't understand this ? -- Justin