Mousius commented on issue #11414: URL: https://github.com/apache/tvm/issues/11414#issuecomment-1158669369
> One recommendation, based on my past experience with large linting or security scan efforts is to open a work item for areas that aren't easily resolved, and leave a comment with the work item number, then address them later, that way we get 90+% of the coverage on existing work, and then can address corner cases individually. Yip, didn't mean to give the wrong impression here, I agree with disabling some bits to enable us to have the linter running 😸 I think all the linting PRs will go in with some `pylint disable` blocks we can use to find them later, that seemed close enough to tracking the work items to me, do you think we need to raise issues for it? As far as I know, replacing `tvm.testing.fixture` with the native `pytest.mark.parameterize` is in the easily resolved category as one is a sugar on top of the other? That way we can use our linter disabling cards for trickier areas? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
