On 2026-06-01 12:24 p.m., Jeff McKenna wrote:
On 2026-06-01 9:54 a.m., Joe Orton wrote:
Windows builds have been failing in CI for a while, I think because of
some changes in the GHA images.
I burnt some Claude tokens trying to fix the trunk to no avail [1], but
I have zero interest in this. It will be ... frustrating... if people
start voting against future 2.4.x rcs because Windows builds are broken
in some way which was trivial to catch in CI and fix ahead of time.
Example trunk failure: https://github.com/apache/httpd/actions/
runs/25912053842/job/76159381743
2.4.x failure is "simpler" because of the cmake version mismatch:
https://github.com/apache/httpd/actions/runs/25488877019/job/74791446628
but working around that as suggested did not help.
Regards, Joe
[1] https://github.com/notroj/httpd/tree/refs/heads/maybe-fix-windows-ci
Branch 2.4.x needs this change to be backported: https://github.com/
apache/httpd/commit/08138ac986851217ff8f03b495d12ceca9051e24
PS. Suggest to use the Backport action in the httpd repo (we use this
and it works beautifully https://github.com/MapServer/MapServer/blob/
main/.github/workflows/backport.yml )
Regarding trunk, there seems to be many changes in trunk that break the
Windows MSVC compiler, it would take me a while to go through all of
those changes (hmm I wonder why those changes made it through your CI
tests / why they were merged before fixing the tests in Windows - as now
it seems like a mountain of fixes are needed)
-jeff
If you don't want to use the automated "Backport" action, then the
equivalent command is "git cherry-pick" to grab that change and apply it
to the 2.4.x branch (I don't have privileges on that repo to do that
command).
Or do you want me to do 2 separate pull requests each time (one into
trunk, and one into 2.4.x)? But that seems odd. But let me know, thanks,
-jeff
-jeff
--
Jeff McKenna
GatewayGeo: Developers of MS4W, & offering MapServer Consulting/Dev
co-founder of FOSS4G
http://gatewaygeo.com/