Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dune doesn't reset DUNE_CACHE_ROOT inside cram tests #11501

Open
davesnx opened this issue Feb 25, 2025 · 1 comment
Open

dune doesn't reset DUNE_CACHE_ROOT inside cram tests #11501

davesnx opened this issue Feb 25, 2025 · 1 comment
Labels
cram Related to the cram test execution in Dune question This issue is a question about something

Comments

@davesnx
Copy link
Contributor

davesnx commented Feb 25, 2025

Opening this issue to see if there's an alternative I'm missing but running dune inside a cram tests makes warnings/hints appear about cache (and most probably any global setup for dune)

If DUNE_CACHE_ROOT is /path/that/does/not/exist/temp this output pops out:

   $ dune build @melange
+  Warning: Cache directories could not be created: Read-only file system;
+  disabling cache
+  Hint: Make sure the directory /path/that/does/not/exist/temp can be created

Reference issue from reasonml/reason-react#870 (comment)

Is there any cache, or set of env variables that should be set on cram tests by users or by default?

@davesnx
Copy link
Contributor Author

davesnx commented Feb 25, 2025

I found this #6138 to be related to the dune's test itself, and @emillon didn't want to disable cache inside cram tests for dune itself.

@maiste maiste added cram Related to the cram test execution in Dune question This issue is a question about something labels Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cram Related to the cram test execution in Dune question This issue is a question about something
Projects
None yet
Development

No branches or pull requests

2 participants