Unit Tests Failing on Windows with File Not Found/File Missing Errors about visqol HOT 5 CLOSED

Hi @iUnknwn ,

Thanks for opening this issue. This is actually a known issue with Bazel on Windows. When I last worked on the Windows unit tests, there was no fix for this. However, I think there might be a solution for this now. You can see this GitHub issues for more details:

• bazelbuild/bazel#3726
• bazelbuild/bazel#5807
• bazelbuild/rules_nodejs#1689

Unfortunately, I no longer have access to a Windows machine for testing any of this. Please feel free to investigate and record any findings here or open a PR!

from visqol.

Hi @FeargusOG - I'll investigate the issues you mentioned, and if I can figure out a way to resolve the issue I'll file a PR.

In the interim, could you perhaps provide basic instructions to run some of the tests manually, such as what are expected scores with some of the sample files (to run as a sanity check post-build)?

from visqol.

Good news - it looks like the tests are now working (I'm assuming that 'too big' error isn't critical, though feel free to correct me):

The relevant bug appears to be this one here: bazelbuild/bazel#8843 - if someone is on Windows 10 version 1703 or newer, and they've enabled Developer Mode, they can run the tests with: bazel test all_unit_tests --enable_runfiles

This will ensure that the test files are symbolically linked in the test directories.

I'll try to submit a PR for the main readme with instructions either today or tomorrow.

from visqol.

Hi @iUnknwn ,

That's great! Thanks for tracking that down and for the readme update. Apologies I didn't get back to you in the meantime with the test results!

from visqol.

The latest windows build passes all c++ tests now.

from visqol.