Skip to content

mix --verbose/MIX_DEBUG=1 does not output enough to understand why the cache is being spoiled #14325

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

Closed
demerphq opened this issue Mar 12, 2025 · 0 comments

Comments

@demerphq
Copy link
Contributor

Elixir and Erlang/OTP versions

$ elixir -v
Erlang/OTP 27 [erts-15.2.2] [source] [64-bit] [smp:11:11] [ds:11:11:10] [async-threads:1] [jit]

Elixir 1.18.2 (compiled with Erlang/OTP 27)

Operating system

macos (N/A)

Current behavior

I was experiencing build cache spoliation due to unknowingly using different versions of elixir to compile a large codebase. Neither MIX_DEBUG=1 nor --verbose helped understand why the cache was being spoiled.

Expected behavior

It would be nice if --verbose or some other option could be used to understand why the cache was being spoiled. IMO if --verbose is being used and the cached is spoiled the output should prominently state why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant