Skip to content

--logfile for libtest doesn't respect --format. #57147

New issue

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

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

Already on GitHub? # to your account

Closed
daxpedda opened this issue Dec 27, 2018 · 1 comment
Closed

--logfile for libtest doesn't respect --format. #57147

daxpedda opened this issue Dec 27, 2018 · 1 comment
Labels
A-libtest Area: `#[test]` / the `test` library C-bug Category: This is a bug. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue.

Comments

@daxpedda
Copy link
Contributor

Observed behaviour
When using for example cargo bench -- -Z unstable-options --format json --logfile bench.json, bench.json has the usual human output format. Stdout prints JSON correctly though.

Expected behaviour
I expect to see JSON output in the file, exactly like in stdout.

Notes
I know at the moment rust is working on the custom test framework (#50297), but other people are still relying on the current features (#51924, rust-lang/cargo#5670).
In any case, I think this is a bug, right? Would love to make a PR.

Rustc
rustc 1.33.0-nightly (a7be40c 2018-12-26)

@epage
Copy link
Contributor

epage commented Feb 11, 2025

--logfile was deprecated in #134283 which freezes the behavior and so I'm going to close this.

@epage epage closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-libtest Area: `#[test]` / the `test` library C-bug Category: This is a bug. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue.
Projects
4 participants