Closed shreyb closed 9 months ago
Before anyone reviews, I'll check to see why the CI tests failed and try to resolve those.
So unfortunately, according to the docs here: https://pylint.pycqa.org/en/latest/user_guide/installation/pre-commit-integration.html, pylint has to be run locally (not inside an isolated environment as pre-commit CI configuration would normally do). As such, I've made it so that the pylint tests work if a developer has installed pre-commit, but are skipped for CI, which they already were. I think as a separate issue, I'll get a github actions container spun up where we can, among unit tests, run pylint on the code base.
It turns out that our pre-commit config was actually not running the pylint tests. I fixed that here. Here are the major changes in this PR:
lib/condor.py
that both the author and reviewer missed. Unit and integration tests passed, so the fact that pylint wasn't working before meant that this was missed when development on that PR was being done. We need to decide whether to fix that issue in this PR, or open a new issue for that. If the latter, we should definitely have it fixed before the next release.