-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
twister: Remove unrecognised sections test #86257
twister: Remove unrecognised sections test #86257
Conversation
145c029
to
1fadc1b
Compare
@@ -483,12 +483,6 @@ def add_parse_arguments(parser = None) -> argparse.ArgumentParser: | |||
action="store_true", | |||
help="Collect and report ROM/RAM section sizes for each test image built.") | |||
|
|||
parser.add_argument( | |||
"--disable-unrecognized-section-test", |
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.
Should we label this option as deprecated first in case it is actually in use somewhere downstream, and keep logging errors as warnings for the same ?
With removing just at the surface as it is currently proposed, why size_calc
still tracks 'recognized' sections ?
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.
While normally deprecation would be in order, notice that we are removing the unrecognised section test altogether, so the --disable-[...]
option is not being deprecated, but becoming the default. Anyone using this option will have the program operation proceed as expected.
Good catch, will remove the recognized
key.
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.
so the
--disable-[...]
option is not being deprecated, but becoming the default.
Anyone using this option will have the program operation proceed as expected.
with this change:
- twister will fail if this option is used somewhere, right ?
- no error logs on unrecognized sections anymore by default
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.
- is the default action now - the check hasn't worked for years.
- I'll add that information to the release notes.
1fadc1b
to
0d79e1e
Compare
3845a2c
to
66ec18f
Compare
The section lists that govern whether the ELF section is recognised or not are out of date. A programming bug has rendered the unrecognised section check unrunnable for years. Thus, the practically dead code of the unrecognised section check is removed in this commit. Signed-off-by: Lukasz Mrugala <lukaszx.mrugala@intel.com>
We remove the --disable-unrecognized..., so we should inform the users of that fact. Signed-off-by: Lukasz Mrugala <lukaszx.mrugala@intel.com>
66ec18f
to
3fa8cfc
Compare
The section lists that govern whether the ELF section is recognised or not are out of date.
A programming bug has rendered the unrecognised section check unrunnable for years.
Fix was attempted in #71051, but lack of updated section lists made the revival of the unrecognised section check counter-productive and undesired.
Thus, the practically dead code of the unrecognised section check is removed in this PR.