happy-pizza-30507
11/21/2021, 12:53 PMpants lint
. I notice that pants 2.9.0.dev2 uses pylint 2.11.0+, which supports --output
option for generating report file. I have that specified as [pylint].args = "--output=./pylint.report.txt"
in pants.toml. I observe that the output isn't printed on the console but, after the run, I can't find the generated report anywhere under the project root. Maybe I forgot to check somewhere else?curved-television-6568
11/21/2021, 6:18 PMoutput=%(buildroot)s/report.txt
happy-kitchen-89482
11/21/2021, 6:22 PMdist/
, but it looks like we don't do that for pylinthappy-kitchen-89482
11/21/2021, 6:22 PMhappy-kitchen-89482
11/21/2021, 6:23 PMhappy-kitchen-89482
11/21/2021, 6:24 PM--output
an absolute path, so you can send that report anywhere...happy-pizza-30507
11/21/2021, 10:03 PM--output=%(buildroot)s/report.txt
. I'm getting the below output when running on osx. Not knowing the exact internals, I guess that the files in buildroot
are being monitored by pants and writing pylint report file right there invalidates the linting process in some way, causing a new job to be rescheduled (and to be invalidated again). Specifying the report under "dist" directory seems to be a better choice.
❯ ./pants lint ::
22:32:51.67 [INFO] Initializing scheduler...
22:32:51.81 [INFO] Scheduler initialized.
22:32:53.62 [INFO] Filesystem changed during run: retrying `Lint` in 500ms...
22:32:54.55 [INFO] Filesystem changed during run: retrying `Lint` in 500ms...
...
Interrupted by user.
hundreds-father-404
11/22/2021, 1:20 AM[GLOBAL].pants_ignore
, list the dist/
folder