Skip to content

Conversation

@qurious-pixel
Copy link
Contributor

Windows ARM build

@schm1dtmac
Copy link
Contributor

schm1dtmac commented Nov 29, 2025

Quick note: I’ve removed googletest in PR #17735 from arm64 CI too to bypass arm64 build lockups but tbh I think in both of our PRs it shouldn't be removed, it’s a workaround for what really is a unit test failure for changes that actually appear to lead to crashes in game on builds that bypass such tests from my tests (see #17746). (That and it’s not uber relevant to Windows ARM CI I guess)

@qurious-pixel
Copy link
Contributor Author

qurious-pixel commented Nov 29, 2025

Quick note: I’ve removed googletest in PR #17735 from arm64 CI too to bypass arm64 build lockups but tbh I think in both of our PRs it shouldn't be removed, it’s a workaround for what really is a unit test failure for changes that actually appear to lead to crashes in game on builds that bypass such tests from my tests (see #17746). (That and it’s not uber relevant to Windows ARM CI I guess)

Thanks @schm1dtmac. I am currently bisecting the googletest issue. test_pair test_simple_array is causing the lockup. I will revert the change, if I can resolve the issue.

@Megamouse Megamouse added OS: Windows Build and CI Anything related to the build process and continuous integration CPU: Arm64 labels Nov 29, 2025
@AniLeo AniLeo requested a review from hcorion December 15, 2025 11:14
@hcorion
Copy link
Member

hcorion commented Dec 21, 2025

Mac tests should be addressed as part of a different PR, but the Windows changes look good

@schm1dtmac
Copy link
Contributor

Mac tests should be addressed as part of a different PR, but the Windows changes look good

Yeah the Mac stuff’s long since been addressed properly and all unit tests succeed now (#17800), so any of that stuff here just needs complete removal.

@kd-11
Copy link
Contributor

kd-11 commented Dec 22, 2025

I'll be able to test this in a few days when I go on break from work.

std::memset(g_range_lock_bits, 0, sizeof(g_range_lock_bits));

#ifdef _WIN32
#if defined(_WIN32) && !defined(__arm64__)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes the following error:

void vm::init() (error=0x8)

vm.cpp error void_mem_error

#if !defined(_MSC_VER) || defined(__clang__)
[[noreturn]] ~throw_exception() = default;
#if defined(__FreeBSD__)
[[noreturn]] ~throw_exception();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why remove the default?
Why exclude all clang?

Copy link
Contributor Author

@qurious-pixel qurious-pixel Jan 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was removed entirely, then hacked back in. not needed anymore after #17899, but should have been a separate PR anyways.

FreeBSD clang behaves differently; it was the only runner to fail after the changes from #17736.

Now all jobs build with L396-398 removed as was inteneded in that PR.

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

Labels

Build and CI Anything related to the build process and continuous integration CPU: Arm64 OS: Windows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants