Skip to content

Fix linter issues related to pylint>=4.0.0#551

Open
oreiche wants to merge 2 commits intomainfrom
oreiche/fix-linter-issues
Open

Fix linter issues related to pylint>=4.0.0#551
oreiche wants to merge 2 commits intomainfrom
oreiche/fix-linter-issues

Conversation

@oreiche
Copy link

@oreiche oreiche commented Jan 14, 2026

test_ui.py:
Fix name style for function constants, which are
deliberately not considered constants anymore.

apport-valgrind:
Remove contradicting control messages, which also triggers
a false positive "useless-suppression" warning.

kernel_oops:
Remove invalid-name suppression, as the new pylint now
correctly identifies those variables not to be constants.

@codecov
Copy link

codecov bot commented Jan 14, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.34%. Comparing base (d3a721e) to head (24e7100).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #551   +/-   ##
=======================================
  Coverage   84.34%   84.34%           
=======================================
  Files         104      104           
  Lines       20814    20814           
  Branches     3254     3254           
=======================================
  Hits        17555    17555           
- Misses       2817     2818    +1     
+ Partials      442      441    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@oreiche oreiche force-pushed the oreiche/fix-linter-issues branch from f4af570 to 6e514e0 Compare January 14, 2026 09:44
from tests.paths import local_test_environment, patch_data_dir, restore_data_dir

ORIGINAL_SUBPROCESS_RUN = subprocess.run
ORIGINAL_SUBPROCESS_RUN = ( # pylint: disable=invalid-name, useless-suppression
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not fix the invalid-name instead?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixing the name would cause older pylint versions (<4.0.0) to complain. Not sure if you want to maintain support for older linter versions (and for how long)?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not need to support older pylint version. You can bump the linter ci to resolute in an additional commit for this PR.

Copy link
Author

@oreiche oreiche Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dropped support for older pylint versions and added an additional commit bumping the linter ci to resolute. PTAL :)

@oreiche oreiche force-pushed the oreiche/fix-linter-issues branch from 6e514e0 to 7fbea47 Compare January 14, 2026 11:07
@bdrung
Copy link
Member

bdrung commented Jan 14, 2026

#552 should land first.

test_ui.py:
  Fix name style for function constants, which are
  deliberately not considered constants anymore.

apport-valgrind:
  Remove contradicting control messages, which also triggers
  a false positive "useless-suppression" warning.

kernel_oops:
  Remove invalid-name suppression, as the new pylint now
  correctly identifies those variables not to be constants.
@oreiche oreiche force-pushed the oreiche/fix-linter-issues branch from 7fbea47 to 24e7100 Compare January 20, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants