Closed lkct closed 10 months ago
(I think this is worth noting in a separate issue)
Inconsistency of pylint results between local runs and workflow runs has long been a problem, e.g., in #162, consider-using-augmented-assign is disabled partially due to this.
consider-using-augmented-assign
This reappeared when #176 is trying to introduce separate rules for tests, c.f., the linting of several force pushes in #176: https://github.com/april-tools/cirkit/actions/runs/7280815126 https://github.com/april-tools/cirkit/actions/runs/7280955595 https://github.com/april-tools/cirkit/actions/runs/7281043514
Comparing the changes and results, it can be inferred that the problem is caused by jobs=0.
jobs=0
TODO: This is not yet a solid proof. If it's confirmed to be multi-processing issue, we can file a bug report for pylint.
(I think this is worth noting in a separate issue)
Inconsistency of pylint results between local runs and workflow runs has long been a problem, e.g., in #162,
consider-using-augmented-assign
is disabled partially due to this.This reappeared when #176 is trying to introduce separate rules for tests, c.f., the linting of several force pushes in #176: https://github.com/april-tools/cirkit/actions/runs/7280815126 https://github.com/april-tools/cirkit/actions/runs/7280955595 https://github.com/april-tools/cirkit/actions/runs/7281043514
Comparing the changes and results, it can be inferred that the problem is caused by
jobs=0
.TODO: This is not yet a solid proof. If it's confirmed to be multi-processing issue, we can file a bug report for pylint.