Possibility of overriding the default test directory location on Windows

[Krande]

Hey,

I was wondering if it's possible to control the location of the test directory.

From what I can tell, setting the --output-dir sets the parent directory for all build-related environments and work directories.

As shown in the figure below, the work directory and build_env/host_env environments are present underneath the --output-dir/bld/<package-name-id>

But for some reason only the test environment is located under the --output-dir/bld/<package-name-id>/work

And the tests are moved to a local temporary directory %AppData%\\Local\\Temp\\.tmpAUNvtX\\conda_build_script.py.

In certain windows enterprise configurations, the user might not have the privileges to run code inside %APPDATA%. So I was wondering if it's possible to get more fine-grained control over the test directory location?

Let me know if you need more information to make sense of my request :)

Best Regards
Kristoffer

[wolfv]

That is indeed something I didn't know / consider before. We can definitely come up with a way to configuring it.

[wolfv]

Suggestions / PRs very welcome! :)

[Krande]

@wolfv I can give it a shot. I guess it boils down to how we'd like to manipulate tmp_dir in https://github.com/prefix-dev/rattler-build/blob/main/src/package_test/run_test.rs#L118 either through using a env var passed as a flag to the cli.

Update:
Or maybe its this tmp_dir? https://github.com/prefix-dev/rattler-build/blob/main/src/package_test/run_test.rs#L564

[Krande]

@wolfv so I made some extremely ugly hacks that at least managed to move the test directory to a subdirectory inside --output-dir in main...Krande:rattler-build:fix/windows-test-directory.

I'll try to find time between other responsibilities to look into this. But if you see any immediate opportunities based on this, feel free to take a stab at it. I can also make a PR with what I have if that's a more convenient place to continue to the conversation :)