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.

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

[logging-too-many-args] Add functional tests for each value of logging-format-style #9121

Merged
merged 2 commits into from
Jun 3, 2024

Conversation

Pierre-Sassoulas
Copy link
Member

@Pierre-Sassoulas Pierre-Sassoulas commented Oct 5, 2023

Type of Changes

Type
βœ“ πŸ› Bug fix

Description

Refs #9118

@Pierre-Sassoulas Pierre-Sassoulas added Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news πŸ”‡ This change does not require a changelog entry labels Oct 5, 2023
@Pierre-Sassoulas Pierre-Sassoulas added False Positive 🦟 A message is emitted but nothing is wrong with the code backport maintenance/3.2.x and removed Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news πŸ”‡ This change does not require a changelog entry labels Oct 5, 2023
@Pierre-Sassoulas Pierre-Sassoulas added this to the 3.0.2 milestone Oct 5, 2023
@Pierre-Sassoulas Pierre-Sassoulas marked this pull request as draft October 5, 2023 20:26
@github-actions

This comment has been minimized.

@DanielNoord
Copy link
Collaborator

@Pierre-Sassoulas Do you have more WIP here? Or shall we close this?

@Pierre-Sassoulas
Copy link
Member Author

Creating regression tests is work too, why throw it away ? But, I don't have the fix atm no.

@Pierre-Sassoulas Pierre-Sassoulas removed the False Positive 🦟 A message is emitted but nothing is wrong with the code label Jun 3, 2024
@Pierre-Sassoulas Pierre-Sassoulas removed this from the 3.2.3 milestone Jun 3, 2024
@Pierre-Sassoulas Pierre-Sassoulas added Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news πŸ”‡ This change does not require a changelog entry labels Jun 3, 2024
@Pierre-Sassoulas
Copy link
Member Author

All right the I was on mobile and didn't see the code. Now that I read it and the context the intent of the MR is due to this : #9118 (comment)

It was hard to reproduce and the current test is not testing each possibility with each values of logging-format-style=new. Actually the new regression test is 4 lines in 2 files and thus hard to copy paste. I think we should merge and acknowledge that there's a false positive, if someone works on it it's going to make their live easier.

@Pierre-Sassoulas Pierre-Sassoulas changed the title [logging-too-many-args] Add a regression test for float formatting [logging-too-many-args] Add functional tests for each value of logging-format-style Jun 3, 2024
@DanielNoord
Copy link
Collaborator

I do think we need to explain why we are mixing old and new style tests in a file that has a docstring of "Tests for logging-too-many-args using old style". That will definitely confuse us later on.

@Pierre-Sassoulas
Copy link
Member Author

It's confusing me right now πŸ˜„

@Pierre-Sassoulas Pierre-Sassoulas marked this pull request as ready for review June 3, 2024 21:18
DanielNoord
DanielNoord previously approved these changes Jun 3, 2024
@Pierre-Sassoulas
Copy link
Member Author

Updated the docstring for clarity, this is ready for review now.

@Pierre-Sassoulas Pierre-Sassoulas enabled auto-merge (rebase) June 3, 2024 21:25
@Pierre-Sassoulas
Copy link
Member Author

Thanks for the review and thanks for the general cleanup earlier Daniel. I did not check everything but I'm not sure we should loose hope on the "need takes over" label and close them all when they age. Some contributors are giving up really close to completion, there's some value in those MR (but we should close low value or unrecoverable one for sure).

@DanielNoord
Copy link
Collaborator

Thanks for the review and thanks for the general cleanup earlier Daniel. I did not check everything but I'm not sure we should loose hope on the "need takes over" label and close them all when they age. Some contributors are giving up really close to completion, there's some value in those MR (but we should close low value or unrecoverable one for sure).

Yeah, those that were close or more recent I kept open. Some of the more controversial ones or low effort ones I closed!

@Pierre-Sassoulas
Copy link
Member Author

Sorry the new comment moved the whole functional test output, had to regenerate πŸ˜…

Copy link

codecov bot commented Jun 3, 2024

Codecov Report

All modified and coverable lines are covered by tests βœ…

Project coverage is 95.82%. Comparing base (4203d87) to head (39038b0).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #9121   +/-   ##
=======================================
  Coverage   95.82%   95.82%           
=======================================
  Files         174      174           
  Lines       18810    18811    +1     
=======================================
+ Hits        18024    18025    +1     
  Misses        786      786           
Files Coverage Ξ”
pylint/checkers/logging.py 94.73% <100.00%> (+0.03%) ⬆️

@Pierre-Sassoulas Pierre-Sassoulas merged commit 86e1943 into pylint-dev:main Jun 3, 2024
44 checks passed
Copy link
Contributor

github-actions bot commented Jun 3, 2024

πŸ€– According to the primer, this change has no effect on the checked open source code. πŸ€–πŸŽ‰

This comment was generated for commit 39038b0

@Pierre-Sassoulas Pierre-Sassoulas deleted the regression-9118 branch June 3, 2024 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news πŸ”‡ This change does not require a changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants