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

Display command that is being run #317

Open
ehuss opened this issue Feb 13, 2024 · 1 comment
Open

Display command that is being run #317

ehuss opened this issue Feb 13, 2024 · 1 comment
Labels
A-ui Area: The CLI and user interface enhancement New feature or request

Comments

@ehuss
Copy link
Collaborator

ehuss commented Feb 13, 2024

It can be helpful if the full command that is being executed is displayed, which can help with debugging issues (such as #284).

I would recommend showing the command with --verbose, along with the environment variables that are set.

@ehuss ehuss added enhancement New feature or request A-ui Area: The CLI and user interface labels Feb 13, 2024
@MingweiSamuel
Copy link

MingweiSamuel commented Apr 11, 2024

Edit: Would be good for --verbose (or -vv) to show the output as well, possibly. It seems --prompt does that a bit, for some reason, #333

Currently trying to bisect a regression in rustc's error output that I found with trybuild, have no idea what cargo-bisect-rustc is doing but it says ERROR: the start of the range (nightly-2024-03-01) must not reproduce the regression even though manually running the command cargo +nightly-2024-03-01 test -p hydroflow --test surface_compile_fail passes as expected. Not sure if trybuild is using the right rust version with bisect. I guess I'll try using --prompt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ui Area: The CLI and user interface enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants