-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pylint/2.16.2: tests failures, test_allow_reexport_package and test_writing_minimal_file #8342
Comments
Thank you for opening the issue, I'm looking into it. Is the latest debian using python 3.11 ? The current test should pass but we're not ready yet (no handling of the new trystar node yet). What's the timeline for a version of pylint to be included in the next release ? |
yes, this is running using python 3.11.2; i noticed some other tests were i can exclude these 2 tests on my end, as i'd like to get pylint into unstable -> testing soon |
What is strange is that we've been testing on python 3.11 for quite some time now. I'm wondering what's different in debian unstable with python 3.11.2 vs our current CI with
Yeah, I think it's safe to ignore temporarily. |
The second issue seems to be caused by a faulty config. The other one is also not related to |
according to pytest, the only plugin loaded is
the diff was part of the original message (altho it may have been hard to find in all that output), so here it is again, hope this helps
|
'Plugin' would be a pylint plugin in this context (hard to check if it's available on your side but I don't see why it would be different in debian unstable). I don't know what could be wrong for this tests. Is there a downladable docker image for unstable debian so we can try to reproduce? Regarding the second fail, the output was truncated automatically which prevent from seeing the full content of the diff. I suppose two new unexpected messages are raised. Could you launch with |
i could provide a long series of steps to reproduce it on your end, but it might be easier if you tell me what to look, as it's straightforward to me to reproduce the problem. for now i did a compulsory grep and i cant find
i thought i did, but here it is again:
|
The expected output is as follows: (Pdb) print(output)
************* Module allow_reexport
tests/regrtest_data/allow_reexport/__init__.py:1:0: C0414: Import alias does not rename original package (useless-import-alias)
************* Module allow_reexport.file
tests/regrtest_data/allow_reexport/file.py:2:0: C0414: Import alias does not rename original package (useless-import-alias) It does feel like we are taking some config from your environment when running the tests and not the one we expect to use. |
It's the same issue in the other test, I'm going to open a MR shortly. |
Closes pylint-dev#8342, but this does not fix the problem generically, all test should run independentely from the system's pylint configuration
Closes pylint-dev#8342, but this does not fix the problem generically, all tests should run independentely from the system's pylint configuration
…8350) * [test] Use an empty pylintrc so tests to not depend on system's conf Closes #8342 * Update tests/checkers/unittest_imports.py Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com> --------- Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com>
…8350) * [test] Use an empty pylintrc so tests to not depend on system's conf Closes #8342 * Update tests/checkers/unittest_imports.py Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com> --------- Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com> (cherry picked from commit 641f526)
I'm going to release 2.16.3 this week with a fix but this should not be a show stopper for debian. Thank you for reporting as always 👍 |
if you have some more cycles, we just got reported https://ci.debian.net/data/autopkgtest/testing/amd64/p/pylint/31703963/log.gz 2 failures in functional tests when running on our CI instance (i can report a separate issue if you prefer) |
…8350) (#8351) * [test] Use an empty pylintrc so tests to not depend on system's conf Closes #8342 * Update tests/checkers/unittest_imports.py Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com> --------- Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com> (cherry picked from commit 641f526) Co-authored-by: Pierre Sassoulas <pierre.sassoulas@gmail.com>
Created #8352 to follow up on this. |
Bug description
when running unittests, 2 tests fail
Command used
Pylint output
Expected behavior
no tests failures
Pylint version
OS / Environment
debian unstable
The text was updated successfully, but these errors were encountered: