-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
inconsistent result in multiple runs #2573
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
Comments
Thanks for the report! multiprocessing might definitely affect this. |
I observe this behavior as well. Most commonly, running with multiple jobs enabled gives false negatives- constraining to -j 1 shows more errors. Here's an easy example:
|
I can reproduce this with the latest version. Should be fixable by using the MapReduceMixin done by @doublethefish in #3458 that was only added to the duplicate checker. |
jaidisido
added a commit
to aws/aws-sdk-pandas
that referenced
this issue
Jun 13, 2022
pylint-dev/pylint#2573 Modifying to `-j 2` to test
Closing as duplicate of #374 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I'm looking into the strange result from pylint on Apache Beam Python SDK. Multiple runs return slightly different results. It looks something related to multi-processing thing because I couldn't find any pattern from this behavior.
Steps to reproduce
0c8ccae9aa608f4d64b22c08d57b9aaa8724bfee
Current behavior
Expected behavior
Consistently return the same result
pylint --version output
Related issue: https://issues.apache.org/jira/browse/BEAM-5846
The text was updated successfully, but these errors were encountered: