The last time we tried this upgrade we encountered timeouts on the quality job, which it now appears were due to the worker running pylint common running out of memory and killing the Jenkins process. Switching to a different worker type with double the RAM (8 GB vs. 4 GB) seems to have fixed this; about 5.5 GB was used. Upstream is aware of the high memory usage on large projects, it's apparently due primarily to a cache of parsed modules: https://github.com/PyCQA/pylint/issues/1495 . Even after disabling some of the new checks that have been added, the new version of pylint found about twice as much to complain about. Just bumping the threshold for now to unblock the Django upgrade, we can try automated utilities like pyupgrade to fix some of these later.
8 lines
158 B
Bash
Executable File
8 lines
158 B
Bash
Executable File
#!/usr/bin/env bash
|
|
set -e
|
|
|
|
export LOWER_PYLINT_THRESHOLD=1000
|
|
export UPPER_PYLINT_THRESHOLD=4050
|
|
export ESLINT_THRESHOLD=5530
|
|
export STYLELINT_THRESHOLD=880
|