-
Notifications
You must be signed in to change notification settings - Fork 389
Pass --color=always through cargo-miri #2243
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
Conversation
with ui tests we could actually test this now, too. It's a bit weird to read as a test, but it would mostly be a canary to detect changes anyway. |
@bors r+ |
📌 Commit 6cd74ee has been approved by |
Btw, I do agree that it would be good to have a test for this, but I've just been poking around in the |
☀️ Test successful - checks-actions |
Yeah it's somewhat chaotic. :/ |
Actually pass through the request for --color=always #2243 actually doesn't work 😂 The suggestion to split on `,` was good but `arg` is actually the whole `--json=diagnostic-rendered-ansi,artifacts,future-incompat `, and of course I didn't test that change locally and we have no test for this in CI. Therefore, I would like some guidance on making a test for this because I'm going to rely on this working.
How could we test this? Our ui tests do not interact with cargo-miri at all so far.
|
I could try adding a |
This was an old email from months ago that github now added to the issue... |
Also this PR has been reverted since: #2283 |
Closes #2037
I just implemented the fix suggested in that issue and it seems to work without issue.