Unable to run mixxx-test.exe on Windows using Visual Studio

[EchoCoder1729]

Bug Description

I could do a Build All successfully and even the mixxx.exe runs but when I try to run mixxx-test.exe I am met with a critical error. I have tried to remove buildenv and reinstall the dependencies but to no avail. I know about the libjack warning, and it is not a critical error however, I can't seem to fix the DEBUG ASSERT error for "pPlayer"

Version

2.6-alpha-83-gcf82b35ea6

OS

Windows 11, Visual Studio 2022

[Swiftb0y]

Thank you for reporting your issue. Please understand that in order for us to be able to properly debug this, we need a backtrace. Have a look at the wiki for finding out how to create one: https://github.com/mixxxdj/mixxx/wiki/Creating%20Backtraces

[EchoCoder1729]

Test Suite output
x64dbg output
Here is the log file from x64dbg and the call stack that I could capture. When I am running x64dbg for mixxx-test.exe, as soon as it crashes, it clears the call stack, so that was difficult to get and maybe incomplete but I copied it into the log as close to the crash as I could.

[Holzhaus]

Does it work if you run the executable via ctest?

[EchoCoder1729]

Do I need to run the executable using ctest or just the specific AutoDJProcessor test?

[JoergAtGithub]

I tried to reproduce this with main, latest VS2022 and latest Windows11. It worked with CTest and GoogleTest. Only the usual #11094 tests failed.

[EchoCoder1729]

Do I need all unit tests to be running to make any successful and working changes? Or do I need to have passed all the unit tests? Also can I just disable some specific tests that are not working from the CMake file?

[JoergAtGithub]

Of cause the unit tests should all Pass. But this seems to be a issue on your local system. As long as your code changes does not break anything that worked before, it shouldn't be an issue.

[EchoCoder1729]

Alright sounds good! Also if there is some other way of running the tests other than mixxx-test.exe, please do let me know. When I tried to use Ctest, it showed that no configuration was found, even when I tried to run the tests separately. Also how do I keep testing after one test fails. It terminates without running all the other tests. Thanks. It's good to have someone on the core team with a windows development environment.

[JoergAtGithub]

You are using VS2022, right?

[EchoCoder1729]

I tried to reproduce this with main, latest VS2022 and latest Windows11. It worked with CTest and GoogleTest. Only the usual #11094 tests failed.

I could also run all the tests that should run using CTest. However, the one test that did not run as was mentioned in #11094 was seekForwardBackward. I see some Disabled Tests in the Google Test Suite. When is a test disabled, and would it make sense to disable this test? Also what is the procedure for disabling test? Just pre-fixing DISABLED_ to to the test name?