You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes Pylint errors are preventing the whole unit tests to run, possibly hiding some further failures.
While in principle it is fine to have a reasonable code before testing, whenever there are Pylint errors are usually localized to some small portions of the code, and they would not cause the whole unit tests to fail.
I propose to make the two jobs independent, even keeping them inside a single workflow. Moreover, we do not need to run Pylint on all the combinations of matrix on which we run unit tests, it is sufficient to iterate Python versions, while linting errors should not depend on the os/architecture.
The text was updated successfully, but these errors were encountered:
Sometimes Pylint errors are preventing the whole unit tests to run, possibly hiding some further failures.
While in principle it is fine to have a reasonable code before testing, whenever there are Pylint errors are usually localized to some small portions of the code, and they would not cause the whole unit tests to fail.
I propose to make the two jobs independent, even keeping them inside a single workflow. Moreover, we do not need to run Pylint on all the combinations of matrix on which we run unit tests, it is sufficient to iterate Python versions, while linting errors should not depend on the os/architecture.
The text was updated successfully, but these errors were encountered: