Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-42015: [MATLAB] Executing tfeather.m test class causes MATLAB to crash on windows-2022 after MSVC update from 14.39.33519 to 14.40.33807 #42123

Merged
merged 4 commits into from
Jun 12, 2024

Conversation

sgilmore10
Copy link
Member

@sgilmore10 sgilmore10 commented Jun 12, 2024

Rationale for this change

After the windows-2022 GitHub runner image was updated last week, MATLAB began crashing when running the unit tests in arrow/matlab/test/tfeather.m on Windows. As part of the update, VS 2022 was updated from
17.9.34902.65 to 17.10.34928.147 and MSVC was updated from 14.39.33519 to 14.40.33807.

It looks like many other projects have run into this issue as well:

  1. New unexpected build failures on 20240603.1.0 actions/runner-images#10004
  2. Broken C++ runtime on windows-2022 version 20240603.1.0 actions/runner-images#10020

The suggested workaround for this crash is to supply the flag _DISABLE_CONSTEXPR_MUTEX_CONSTRUCTOR when building.

What changes are included in this PR?

  1. Supply _DISABLE_CONSTEXPR_MUTEX_CONSTRUCTOR flag when building Arrow C++.

Are these changes tested?

N/A. Existing tests used.

Are there any user-facing changes?

No.

@sgilmore10
Copy link
Member Author

I believe the Dev/Lint C++, Python, R , Docker, RAT workflow is timing out. I'll try re-running it.

@sgilmore10
Copy link
Member Author

+1

@sgilmore10 sgilmore10 merged commit 512d245 into apache:main Jun 12, 2024
9 checks passed
@sgilmore10 sgilmore10 deleted the GH-42015 branch June 12, 2024 17:22
@sgilmore10 sgilmore10 removed the awaiting review Awaiting review label Jun 12, 2024
Copy link

After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 512d245.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 23 possible false positives for unstable benchmarks that are known to sometimes produce them.

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

Successfully merging this pull request may close these issues.

None yet

1 participant