linting in CI works differently than locally about clusterfuzz HOT 8 CLOSED

That's really strange...

$ sudo docker run --rm -ti -v $(pwd)/clusterfuzz:/workspace gcr.io/clusterfuzz-images/ci /bin/bash
root@6bcbbf462031:/workspace# pylint --version
No config file found, using default configuration
pylint 1.9.3, 
astroid 1.6.5
Python 2.7.12 (default, Nov 12 2018, 14:36:49) 
[GCC 5.4.0 20160609]
root@6bcbbf462031:/workspace# pylint src/appengine/handlers/upload_testcase.py
No config file found, using default configuration
************* Module src/appengine/handlers/upload_testcase.py
F:  1, 0: No module named src/appengine/handlers/upload_testcase.py (fatal)

from clusterfuzz.

My ENV version is also 1.9.3, but also cannot find this.

from clusterfuzz.

Actually, I may have spoke too soon about 1.9.4 being the fix.
But the part about being unable to repro locally is true. Maybe it's because we have some deps installed in CI that pylint is looking at, but not locally?

from clusterfuzz.

I think the issue may be PYTHONPATH.

In the CI, we have /data/google_appengine:/workspace/src. If I remove the app engine path, it no longer reports that issue. Maybe it's exiting early when it can't import the appengine modules.

from clusterfuzz.

I think the issue may be PYTHONPATH.

Sounds correct to me. I don't actually think it has to do with using 1.9.4 (I think I thought this because of similar issues that came up when I used pylint in a fresh virtualenv)

from clusterfuzz.

It seems to me the pylint result from CI is more accurate than my local one. Do you think the fix is to make CI like local? It seems like making local like pylint on CI is the more ideal fix no?

from clusterfuzz.

Race: looks like you decided this :)

from clusterfuzz.

Yup :) Looks like local was missing results.

from clusterfuzz.