GH-47234: [C++][Python] Add test for fill_null regression on Windows#47249
GH-47234: [C++][Python] Add test for fill_null regression on Windows#47249pitrou merged 5 commits intoapache:mainfrom
Conversation
|
@github-actions crossbow submit wheel-windows-* |
There was a problem hiding this comment.
@amoeba following your repro I'm trying the same in cpp.
|
@github-actions crossbow submit wheel-windows-* |
|
Revision: 2a5b093fe13beebfe5f690ba9221a4333e22b00d Submitted crossbow builds: ursacomputing/crossbow @ actions-6614a425dd |
|
@github-actions crossbow submit wheel-windows-cp313-cp313-amd64 |
|
Revision: 85a2071aae01eeda65449b35599c13ee5c3606f7 Submitted crossbow builds: ursacomputing/crossbow @ actions-53ecca2d5e
|
|
@github-actions crossbow submit wheel-windows-cp313-cp313-amd64 |
This comment was marked as outdated.
This comment was marked as outdated.
ca3a37b to
6191313
Compare
|
@github-actions crossbow submit wheel-windows-cp313-cp313-amd64 |
|
Revision: 61913132ee21b589a1f1baddbc6df9f05488ef52 Submitted crossbow builds: ursacomputing/crossbow @ actions-28a873a6f2
|
|
@github-actions crossbow submit wheel-windows-cp313-cp313-amd64 |
|
(retrying a new build, who knows, perhaps something was fixed?) |
|
Revision: 61913132ee21b589a1f1baddbc6df9f05488ef52 Submitted crossbow builds: ursacomputing/crossbow @ actions-184d8e9469
|
6191313 to
483d497
Compare
|
@github-actions crossbow submit wheel-windows-cp313-cp313-amd64 |
This comment was marked as outdated.
This comment was marked as outdated.
483d497 to
a24190d
Compare
|
@github-actions crossbow submit wheel-windows-cp313-cp313-amd64 |
|
Revision: a24190d14e4fe0966216efd33ed5e52ce1cc155d Submitted crossbow builds: ursacomputing/crossbow @ actions-ffeb60e918
|
|
Perhaps this requires #47455 for the cpp regression test? Currently, no cpp tests are running on Windows CI |
|
No, we're really running the Python tests here. |
a24190d to
289eea8
Compare
|
@github-actions crossbow submit wheel-windows-cp313-cp313-amd64 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
@github-actions crossbow submit -g cpp |
|
Revision: 289eea8 Submitted crossbow builds: ursacomputing/crossbow @ actions-2547cd8dd3
|
|
Revision: 289eea8 Submitted crossbow builds: ursacomputing/crossbow @ actions-f189892110 |
289eea8 to
24e90dd
Compare
|
@github-actions crossbow submit -g wheel |
|
|
|
Revision: 24e90dd Submitted crossbow builds: ursacomputing/crossbow @ actions-2d68d9e6cc |
|
Let's check that all wheel builds are ok now. If ok, then this PR will be mergeable. |
|
The failing wheel builds also failed on the nightlies. Will merge. |
|
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 4630313. There weren't enough matching historic benchmark results to make a call on whether there were regressions. The full Conbench report has more details. |
…ndows (apache#47249) ### Rationale for this change Add regression test for an issue that surfaced on specific MSVC versions, presumably due to a compiler bug. Possible upstream tickets are https://developercommunity.visualstudio.com/t/Code-optimization-bug-SIMD-std::transf/10912292 and https://developercommunity.visualstudio.com/t/SIMD-Code-optimization-bug/10945478. ### What changes are included in this PR? Additional tests to catch any further occurrence of this specific problem. ### Are these changes tested? Obviously yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#47234 Lead-authored-by: Antoine Pitrou <antoine@python.org> Co-authored-by: Rok Mihevc <rok@mihevc.org> Co-authored-by: Antoine Pitrou <pitrou@free.fr> Signed-off-by: Antoine Pitrou <antoine@python.org>
Rationale for this change
Add regression test for an issue that surfaced on specific MSVC versions, presumably due to a compiler bug.
Possible upstream tickets are https://developercommunity.visualstudio.com/t/Code-optimization-bug-SIMD-std::transf/10912292 and https://developercommunity.visualstudio.com/t/SIMD-Code-optimization-bug/10945478.
What changes are included in this PR?
Additional tests to catch any further occurrence of this specific problem.
Are these changes tested?
Obviously yes.
Are there any user-facing changes?
No.