-
Notifications
You must be signed in to change notification settings - Fork 687
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
Resolve linting issues, consolidate linting makefile targets #4432
Conversation
7a501ee
to
bfde353
Compare
|
This does not pass locally. Is this meant to be run in the dev container?
|
@heartsucker I think you just need to rebuild your virtualenv. It's missing pyenchant. I also ran into an error during |
To accomplish this, I ran As for the CI failure, let's consider baking the |
Built a new CI image (version-controlled outside of this repository), and pushed a small commit to retrigger a build. Let's monitor CI and see how it fares. |
CI failed at
Rerunning to check if flake... |
New CI box is reliably failing when staging VMs come back up after a reboot, as above. That's something we should look into fixing, but to unblock this PR, I'm going to delete the new box and add a task to install enchant inside the CI box on PR run, as originally suggested. |
Update: the naive approach in ae3938f isn't sufficient for the CI environment, specifically because the remote user lacks sudo rights (all SD dev env operations are run as a normal user during the CI job). We can work around that, specifically by using the |
tons of false positives, we can re-enable this later
the choice here is to: 1. install enchant in the staging machine 2. break up development dependencies into what is needed for linting and what is needed for the provisioning of staging machines selecting the former, as having too many requirements files has caused major confusion in the past.
0b6e3fa
to
b1313b1
Compare
Rebuilds the GCP CI box on Stretch, rather than Xenial. Doing so fixed a recurring problem during the "make staging" run where the staging VMs did not come back up, causing Ansible to timeout during wait, and the entire build to fail.
06201c9
to
45b7139
Compare
Codecov Report
@@ Coverage Diff @@
## develop #4432 +/- ##
========================================
Coverage 83.72% 83.72%
========================================
Files 44 44
Lines 2956 2956
Branches 321 321
========================================
Hits 2475 2475
Misses 404 404
Partials 77 77 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finally all CI green and it looks good to me. Approved.
Status
Ready for review
Description of Changes
Changes proposed in this pull request:
make ci-lint
jobmake lint
(takes a while and is annoying when working on code only)Testing
make lint
locally, ensure all passesDeployment
CI/dev only
Checklist
If you made changes to the server application code:
make lint
) and tests (make -C securedrop test
) pass in the development containerIf you made non-trivial code changes: