8000 Erroneous deprecation warning · Issue #909 · gcovr/gcovr · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Erroneous deprecation warning #909

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
Tsche opened this issue Mar 27, 2024 · 1 comment · Fixed by #912
Closed

Erroneous deprecation warning #909

Tsche opened this issue Mar 27, 2024 · 1 comment · Fixed by #912

Comments

@Tsche
Copy link
Contributor
Tsche commented Mar 27, 2024

When executing gcovr with -u, --sort-uncovered, -p or --sort-percentage gcovr emits a message like

Deprecated, please use '--sort-key uncovered-number' instead. 

Running gcovr with --sort-key uncovered-number however emits an error

gcovr: error: unrecognized arguments: --sort-key uncovered-number

The actual argument is called --sort, not --sort-key. See configuration.py lines 535-549.

Either the deprecation warnings should be updated or the command line argument --sort renamed to match the configuration key. Please let me know which option you prefer, I'm happy to contribute the change myself.

@Spacetown
Copy link
Member

I prefer to update the deprecation warning because the documentation uses the option --sort.

craigbarnes added a commit to craigbarnes/dte that referenced this issue Jul 6, 2024
The warning is displayed as:

> (WARNING) Deprecated option --sort-percentage used, please use
> '--sort-key uncovered-percent' instead.

However, the suggested `--sort-key` option doesn't actually exist and
is really named `--sort` (both in the documentation and the code).

See also: gcovr/gcovr#909
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0