Skip to content

[Bugfix]: Windows CI stability #306

Closed

Description

@general-kroll-4-life

Background

The following windows CI steps fail frequently:

  • Set up mingw
  • Choco install postgres

Acceptance criteria

  • Root cause for instability identified.
  • Either:
    • (a) implement a fix / mitigation, immediately.
    • (b) document a strategic state including justification for delay in implementation.

Examples:

Error log from Set up mingw:

Chocolatey v2.2.2
Upgrading the following packages:
mingw
By upgrading, you accept licenses for the packages.

mingw v8.1.0 [Approved]
mingw package files upgrade completed. Performing other installation steps.
Downloading mingw 64 bit
  from 'https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/8.1.0/threads-posix/seh/x86_64-8.1.0-release-posix-seh-rt_v6-rev0.7z/download'
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/8.1.0/threads-posix/seh/x86_64-8.1.0-release-posix-seh-rt_v6-rev0.7z/download'. Exception calling "GetResponse" with "0" argument(s): "The request was aborted: Could not create SSL/TLS secure channel." 
This package is likely not broken for licensed users - see https://docs.chocolatey.org/en-us/features/private-cdn.
The upgrade of mingw was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\mingw\tools\chocolateyinstall.ps1'.
 See log for details.

Chocolatey upgraded 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - mingw (exited 404) - Error while running 'C:\ProgramData\chocolatey\lib\mingw\tools\chocolateyinstall.ps1'.
 See log for details.
Error: Process completed with exit code 1.

Activity

  1. converted this from a draft issue on Oct 9, 2023
  2. jeffreyaven commented on Nov 13, 2026

    @jeffreyaven
    Member

    The historical Windows CI failure modes have been addressed through pure-Go builds in #786, retry handling in #775, and Windows installation/probe hardening in #864. Closing this historical stability bucket. Any new failure should be reported separately with its workflow run and failing step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions