git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Toon Claes <toon@iotcl.com>
To: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: [PATCH 3/5] gitlab-ci: drop workaround for Python certificate store on Windows
Date: Mon, 06 Oct 2025 12:19:12 +0200	[thread overview]
Message-ID: <875xcsbae7.fsf@iotcl.com> (raw)
In-Reply-To: <20251002-pks-gitlab-ci-windows-improvements-v1-3-6a8b6b45d728@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> On Windows, we have been running into some issues in the past where the
> certificate store for Python is broken on the GitLab CI runners using
> Windows. The consequence was that we weren't able to establish any SSL
> connections via Python, but we need that feature so that we can download
> the Meson wraps. The workaround we employed was to import certificates
> from the cURL project into the certificate store via OpenSSL.
>
> This is obviously an ugly workaround. But even more importantly, this
> workaround fails every time Chocolatey updates its OpenSSL packages. The
> problem here is that the old OpenSSL package installer will be removed
> immediately once the newer version was published, But the Chocolatey
> community repository may not yet have propagated the new version of this
> package to all of its caches. The result is that for a couple hours (or
> sometimes even one or two days) we always fail to install OpenSSL until
> the new version was propagated.
>
> Luckily though, it turns out that the workaround doesn't seem to be
> required anymore. Drop it to work around the intermittent failures and
> to clean up some now-unneeded legacy cruft.

I assume this is a result of this change:
https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/gcp/windows-containers/-/merge_requests/72

Makes sense to clean this up.

-- 
Cheers,
Toon

  reply	other threads:[~2025-10-06 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 11:04 [PATCH 0/5] gitlab-ci: some fixes for failures on Windows Patrick Steinhardt
2025-10-02 11:04 ` [PATCH 1/5] gitlab-ci: dedup instructions to disable realtime monitoring Patrick Steinhardt
2025-10-02 11:04 ` [PATCH 2/5] gitlab-ci: ignore failures " Patrick Steinhardt
2025-10-02 11:04 ` [PATCH 3/5] gitlab-ci: drop workaround for Python certificate store on Windows Patrick Steinhardt
2025-10-06 10:19   ` Toon Claes [this message]
2025-10-02 11:04 ` [PATCH 4/5] gitlab-ci: upload Meson test logs as JUnit reports Patrick Steinhardt
2025-10-02 11:04 ` [PATCH 5/5] t8020: fix test failure due to indeterministic tag sorting Patrick Steinhardt
2025-10-02 11:10   ` Kristoffer Haugsbakk
2025-10-02 11:24     ` Patrick Steinhardt
2025-10-06 10:20   ` Toon Claes

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875xcsbae7.fsf@iotcl.com \
    --to=toon@iotcl.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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.
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 NNTP newsgroup(s).