You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[C++] AssertTestWithinUlp.Basics Test Fails on Windows #47442
Describe the bug, including details regarding any error messages, version, and platform.
As discovered in #47282 (comment), this test actually does not pass on Windows. At the moment, our CI is inadvertently not running it (see #47434), but this should be fixed anyway
I reproduced a related failure-reporting problem on Windows x64, Arrow main at a907fbc, MSVC 19.44 and bundled GoogleTest 1.18.0: a test using an exported ArrowTesting assertion prints six assertion failures, but exits 0 and records zero failures in XML. A static-runtime control correctly exits 1 and records the failed test.
The shared build loads different GoogleTest state in the runner (arrow_gmock_main.dll) and the assertion helpers (arrow_gtest.dll, via arrow_testing.dll). On MSVC, Google Mock's DLL targets embed GoogleTest rather than sharing the standalone GTest DLL.
I am testing a focused shared-runtime linkage fix, including ArrowTesting's installed dependency metadata. The regressions also restore the Windows checks associated with this issue, so the build can establish whether they were failing because their expected assertions reached another reporter. This follows #47434/#47455 and the earlier #4380 work (integrated as c39db99), rather than a new-discovery claim.
This work is AI-assisted; I will include the executed native tests and configuration limits with the patch.
Activity
[-]AssertTestWithinUlp.Basics Test Fails on Windows[/-][+][C++] AssertTestWithinUlp.Basics Test Fails on Windows[/+]xgbtxy commentedon Oct 20, 2026
I reproduced a related failure-reporting problem on Windows x64, Arrow main at a907fbc, MSVC 19.44 and bundled GoogleTest 1.18.0: a test using an exported ArrowTesting assertion prints six assertion failures, but exits 0 and records zero failures in XML. A static-runtime control correctly exits 1 and records the failed test.
The shared build loads different GoogleTest state in the runner (
arrow_gmock_main.dll) and the assertion helpers (arrow_gtest.dll, viaarrow_testing.dll). On MSVC, Google Mock's DLL targets embed GoogleTest rather than sharing the standalone GTest DLL.I am testing a focused shared-runtime linkage fix, including ArrowTesting's installed dependency metadata. The regressions also restore the Windows checks associated with this issue, so the build can establish whether they were failing because their expected assertions reached another reporter. This follows #47434/#47455 and the earlier #4380 work (integrated as c39db99), rather than a new-discovery claim.
This work is AI-assisted; I will include the executed native tests and configuration limits with the patch.
apacheGH-47442: Limit reporter checks for static GoogleTest on Windows