Skip to content

Tests: address new pylint warnings #1674

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

Merged
merged 1 commit into from
Nov 16, 2021

Conversation

MVrachev
Copy link
Collaborator

Description of the changes being introduced by the pull request:
After the recent changes, there are a couple of new pylint warnings that
appeared.
They are caused by the new test file that was added
test_updater_top_level_update.py and the limit of public functions was
reached in the TestMetadata class in test_api.py
The warnings should be addressed before enabling all of the linters
on the tests files.

Signed-off-by: Martin Vrachev [email protected]

Please verify and check that the pull request fulfills the following
requirements
:

  • The code follows the Code Style Guidelines
  • Tests have been added for the bug fix or new feature
  • Docs have been added for the bug fix or new feature

After the recent changes there are a couple of new pylint warnings that
appeared.
They are caused by the new test file that was added
test_updater_top_level_update.py and the limit of public functions was
reached in the TestMetadata class in test_api.py
The warnings should be addressed before enabling all of the linters
on the tests files.

Signed-off-by: Martin Vrachev <[email protected]>
@coveralls
Copy link

Pull Request Test Coverage Report for Build 1453649624

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 97.461%

Totals Coverage Status
Change from base Build 1449719184: 0.0%
Covered Lines: 3946
Relevant Lines: 4030

💛 - Coveralls

@jku
Copy link
Member

jku commented Nov 15, 2021

It's not a problem to add a few fixes like this in the lint enabling PR: that's sort of expected since the code evolves all the time...

Copy link
Member

@jku jku left a comment

Choose a reason for hiding this comment

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

these look fine to me (but feel free to include in lint enabling PR as well).

If we keep adding too many pylint disables, we might want to actually define a separate pylint profile for tests... but for now this seems fine

@jku jku merged commit ec285a4 into theupdateframework:develop Nov 16, 2021
@MVrachev MVrachev deleted the pylint-more-changes branch December 10, 2021 12:00
@lukpueh lukpueh mentioned this pull request Dec 13, 2021
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.

3 participants