-
Notifications
You must be signed in to change notification settings - Fork 435
odoc required by cram depending on objs/byte #11633
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
Comments
Here is a repro cram test:
|
Here is the reason:
We are storing |
One way you can exclude is to do:
since all the files you are interested in have a |
Brilliant! Thanks for the workaround. BTW, don't you think it would be nice to have something like |
I'm not sure what exactly we would include in such a However I suppose the more idiomatic way to do what you want would be:
if there are other compilation artefacts that you require and are not listed here: https://dune.readthedocs.io/en/stable/advanced/variables-artifacts.html#variables-for-artifacts then we could definitely consider adding them. |
Maybe we could the odoc artifacts into their own object directory. Shouldn't be too hard and it does seem like the safer default. |
Uh oh!
There was an error while loading. Please reload this page.
Expected Behavior
Actual Behavior
Reproduction
dune-project
with(lang dune 3.18)
foo.ml
andfoo.t
dune
file:dune runtest
Specifications
Additional information
Local switch contents
The text was updated successfully, but these errors were encountered: