strange raja test compile errors on windows

[cyrush]

strange raja test compile errors on windows

[rhornung67]

@cyrush thanks for the info. Although it's not perfect, our system of naming each test file attempts to make clear what RAJA features are being tested. Our tests are highly parametrized where we minimize the amount of test code we maintain and specialize based on features that are tested by generating files during CMake configuration. It helps preserve our sanity, but clearly we did not think about name length constraints in different environments. This will require some mulling to resolve.

[cyrush]

Well, it turns out all folders seem to show "possibly read only", so this might not be the source of my problem.

[cyrush]

I found the source of the problem.

The generated file names are simply too long.

Windows APIs have a default max length of 260 chars.

Example of not working: Path that is 263 chars long:

C:\Users\cyrus\Documents\GitHub\ascent\scripts\build_ascent\build\raja-v2022.10.4\test\functional\kernel\basic-single-loop\test-kernel-resource-basic-single-loop-Segments-Sequential.exe.dir\Debug\test-kernel-resource-basic-single-loop-Segments-Sequential.exe.log 

Example of working: Path that is 253 chars long:

C:\Users\cyrus/Documents/GitHub/ascent/scripts/build_ascent/build/raja-v2022.10.4/test/functional/kernel/basic-fission-fusion-loop/test-kernel-basic-fission-fusion-loop-Sequential.exe.dir/Release\test-kernel-basic-fission-fusion-loop-Sequential.exe.log

I hand edited to reduce the size of the filename of one of the cases and yes, I was able to to build.

Also:

• I tried to enable some windows policies to get around the issue, but that wasn't fruitful.
• I tried setting CMAKE_OBJECT_PATH , which did not help.

Maybe we should employ a remove all vowels from source file names policy? :-)

[cyrush]

totally understand, long paths are reasonable -- just sad that windows doesn't concur :-(

[rhornung67]

Closing since issue is understood. Can re-open if becomes a bigger problem.