Fix Pylint violations (easy) - #7013
Conversation
|
Thanks for the pull request, @stvstnfrd! I've created OSPR-412 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams. Feel free to add as much of the following information to the ticket:
All technical communication about the code itself will still be done via the Github pull request interface. As a reminder, our process documentation is here. |
There was a problem hiding this comment.
Are we certain that nothing relies on depth as a positional argument?
There was a problem hiding this comment.
My extensive grepping reveals no matches.
There was a problem hiding this comment.
I found this hard to believe at first, but looking at the function signature for other definitions of get_courses, (self, **kwargs) seems to actually match what we already have elsewhere.
|
👍 Also, it looks like the Jenkins build only failed because of the newly-exposed pylint violations, which were actually there the whole time. For example, empty docstrings are worse than no docstrings at all, but pylint didn't catch the empty docstrings. I think this PR is ready to merge, despite the Jenkins "failure". |
|
@singingwolfboy Yeah, it looks like the only "failures" are from 4
Each of these issues was already present; they're just being exposed to The But to re-emphasize, these issues already existed in the code, so I'd |
|
@stvstnfrd generally I think I agree, that it's fine to merge this without a fully-passing build. Let me take a shot at reviewing this first. |
|
@stvstnfrd this drops us to 6044 pylint violations. Personally I think it'd be best to adjust the |
|
@sarina I agree; allow me to tack on an additional commit to drop the threshold. |
|
I have added an additional commit to lower the threshold at 0e997c7. |
There was a problem hiding this comment.
Can we move this comment to above L12, so we understand why we need the pragma?
There was a problem hiding this comment.
durrrhh nevermind realized L12 is actually a removal not an addition n/m
0e997c7 to
9b7a69a
Compare
|
👍 once last 2 comments addressed. |
|
@sarina I have removed the useless test and added a TODO comment about fixing the other test later. |
|
Huh - it doesn't seem like the build is actually running. I wonder if you're lacking some of the infrastructure to make our recent Jenkins upgrades run properly. I'm going to cancel the build, and if you could rebase this, we'll see if that gets the build going properly. |
Per @sarina: > `build_problem` is called in `_make_problem`, which other tests call > in this class. A failure here will arise in other tests. This test is > unnecessary.
6a0c0b1 to
237f2c3
Compare
|
I'm working with test eng to get the build stuff straightened out - it's not running properly, not your fault at all. Will merge as soon as I can get it all figured out. |
|
test this please |
|
No worries; let me know how I can help. |
|
test this please |
|
ok to test |
|
Alright the failing tests on this branch are flaky and I believe are already disabled in master. Plus they passed on the lbuild I ran on my identical branch (#7049). |
|
w00t! I'll try to assemble another set this weekend! |
This is a subset to partially replace #7008.
@sarina You were right; piecemeal is the way to go here.
This set should be pretty easy to review; most of these are self-evident without context (the fun comes later).