[3.2] Some AppVeyor CI jobs can't run go-httpbin any more (Issue #26232)
VZ
vadz created an issue (wxWidgets/wxWidgets#26232)I don't know when it happened, but currently "TOOLSET=nmake, VS=9.0, BUILD=release, ARCH=x86" and "TOOLSET=cmake, GENERATOR=Visual Studio 12, SHARED=ON, CONFIGURATION=Release" jobs consistently fail with the not very useful error, see e.g. this run:
--- httpbin output ---
go-httpbin : time=2026-02-23T15:33:29.558Z level=INFO msg="go-httpbin listening on http://127.0.0.1:8081"
At line:1 char:2
+ go-httpbin -host 127.0.0.1 -port 8081 2>&1 > c:\projects\wxwidgets\h ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (time=2026-02-23...127.0.0.1:8081":String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
time=2026-02-23T15:33:34.376Z level=INFO msg="200 GET /ip 0.0ms" status=200 method=GET uri=/ip size_bytes=28 duration_ms=0 user_agent=curl/7.55.1 client_ip=127.0.0.1
No idea what's going on here, but it looks like our test for launching go-httpbin passes and then we somehow get the error later?
I'll probably just disable these tests for these jobs, but it's rather puzzling.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26232)Oh, this could be a worse problem than I thought. It looks like the tests just fail without any information in these configurations, at least disabling the use of go-httpbin didn't fix anything, see e.g. this run.
I have no idea if it's something in our code or something on AppVeyor that broke this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26232)This run succeeded for 039a6c9 (Backport CMake changes, 2026-02-21) but this one failed for b83d79b (Fix several memory leaks in wxOSX, 2026-02-22) which is the next commit in the branch which can't affect AppVeyor because it only touched wxOSX sources.
So this definitely looks like an AppVeyor problem, and it looks like we don't have any choice but to stop running the tests entirely in these jobs :-(
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.