-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[tools] Try to fix bloat check when comment has empty cell #26479
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pullapprove
bot
requested review from
amitnj,
anush-apple,
arkq,
bzbarsky-apple,
carol-apple,
cecille,
chrisdecenzo,
chshu,
chulspro,
cliffamzn,
CodeChronos928,
dhrishi,
electrocucaracha,
franck-apple,
gjc13,
harimau-qirex,
harsha-rajendran,
hawk248,
jelderton,
jepenven-silabs,
jmartinez-silabs,
jmeg-sfy,
joonhaengHeo,
jtung-apple,
kkasperczyk-no,
ksperling-apple,
lazarkov,
lpbeliveau-silabs,
LuDuda and
mlepage-google
May 10, 2023 15:46
pullapprove
bot
requested review from
saurabhst,
selissia,
sharadb-amazon,
tcarmelveilleux,
tecimovic,
tehampson,
turon,
vijs,
vivien-apple,
woody-apple,
xylophone21,
younghak-hwang and
yufengwangca
May 10, 2023 15:46
Damian-Nordic
force-pushed
the
bloat-check
branch
from
May 10, 2023 15:46
76961da
to
d9e3652
Compare
PR #26479: Size comparison from 95acf3d to d9e3652 Increases (1 build for cc32xx)
Decreases (1 build for nrfconnect)
Full report (7 builds for cc32xx, linux, mbed, nrfconnect)
|
andy31415
reviewed
May 10, 2023
andy31415
approved these changes
May 10, 2023
bzbarsky-apple
approved these changes
May 11, 2023
Damian-Nordic
force-pushed
the
bloat-check
branch
from
May 11, 2023 07:03
d9e3652
to
63a8ec3
Compare
PR #26479: Size comparison from 8635ca4 to 63a8ec3 Decreases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
The bloat check has been failing for months now because gh_report.py script seems to assume that the first row in a comment to the analyzed PR has no empty cells, and for the cc32xx platform, which happens to finish the build as the first one, a row with a blank section name is added. I don't know what is the reason of the blank section, but the script should not give up just because of one invalid entry as we miss important code size increase warnings. Also, replace deprecated DataFrame.append with concat().
Damian-Nordic
force-pushed
the
bloat-check
branch
from
May 11, 2023 09:29
63a8ec3
to
cd51370
Compare
PR #26479: Size comparison from bb3ce44 to cd51370 Increases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The bloat check has been failing for months now because gh_report.py script seems to assume that the first row in a comment to the analyzed PR has no empty cells, and for the cc32xx platform, which happens to finish the build as the first one, a row with a blank section name is added.
I don't know what is the reason of the blank section, but the script should not give up just because of one invalid entry as we miss important code size increase warnings.