-
-
Notifications
You must be signed in to change notification settings - Fork 394
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
bugfix: compile ... --dump-profile
now produces a clean output
#2852
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2852 +/- ##
==========================================
+ Coverage 67.73% 67.87% +0.13%
==========================================
Files 238 238
Lines 22402 22412 +10
==========================================
+ Hits 15175 15212 +37
+ Misses 6033 6005 -28
- Partials 1194 1195 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LTGM but
It might be a good idea to have them ORed. WDYT? |
Do you mean XORed?
vs
|
With ORed, I mean showing both the verbose output and dumping the profile, but I don't know if it is a good idea. It may be better to separate the two features. I let you have the last word. |
Ah, no then, I'll keep it as in this PR. |
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
When a
compile --dump-profile
is performed, the output is the clean profile that could be redirected in a file.What is the current behavior?
A regression in the Arduino CLI 1.2.0 made the profile disappear from the non-verbose output:
the only way to get the profile with --dump-profile is to enable verbose -v, but this is really inconvenient:
What is the new behavior?
Does this PR introduce a breaking change, and is titled accordingly?
Other information
Fix #2848