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.

Sign up for GitHub

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

Jump to bottom

Cargo warnings/errors are not propagated when building target application #50

Open
tmplt opened this issue Oct 27, 2021 · 4 comments
Open

Cargo warnings/errors are not propagated when building target application #50

tmplt opened this issue Oct 27, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@tmplt
Copy link
Member

tmplt commented Oct 27, 2021

For example: non-applied patches.
@tmplt tmplt added the bug Something isn't working label Oct 27, 2021
@tmplt tmplt added this to the v0.3.0 milestone Oct 27, 2021
@tmplt
Copy link
Member Author

tmplt commented Oct 27, 2021

It seems like the build progress of the target application is not printed either.

@tmplt
Copy link
Member Author

tmplt commented Oct 27, 2021

Build progress seems like a no-go with current release of cargo_metadata with latest stable cargo. Not sure why that is the case. But errors are printed as expected. Unknown if warnings are printed.

@tmplt
Copy link
Member Author

tmplt commented Oct 28, 2021

rustc warnings are emitted.

@tmplt tmplt removed this from the v0.3.0 milestone Oct 29, 2021
@tmplt
Copy link
Member Author

tmplt commented Oct 31, 2021

Cargo errors can be reproduced by (for example) trying to fetch cortex-m-rtic-trace from an invalid repository.

@tmplt tmplt changed the title Cargo warnings are not propagated when building target application Cargo warnings/errors are not propagated when building target application Oct 31, 2021
tmplt added a commit that referenced this issue Nov 1, 2021
@tmplt
scope/build: add hints for cargo errors
a819308 
Regression: cargo errors/warnings are not propagated as expected. This
is a quick fix to let the user know how to see them until #50 is fixed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tmplt