-
Notifications
You must be signed in to change notification settings - Fork 52
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
22.9.1: pytest is failing in pydoctor/test/test_cyclic_imports_base_classes.py::test_cyclic_imports_base_classes
unit
#670
Comments
Hi, Looks like you have already opened an issue about this: #556. Since the test is successful in our CI, I don't know what to say other than to make importable the |
Did you try to reporoduce that issue using described method? |
No I haven’t reproduced the error. And it’s not really an issue in my perspective since the test passes in our CI. The error your facing most probably reside in the fact that you rely on custom PYTHONPATH instead of using the default. That environment variable does not get passed to the sub process running this test, so it can’t find the module. |
So how to pass it? 🤔 |
Two solutions: 1. You deselect the test and we don’t talk about it anymore, cause after all it’s not an issue with the software. 2. You patch the test so it passes on your environment by passing along the environment variable |
Hmm .. issue has been resolved? 🤔 |
This test is correctly running in our CI, so it's not an issue IMO. If you like to submit a PR that fixes your problem, I'll have a look :) |
Did you had a look at least on list of modules with versions which I've used? |
No. If YOU want to contribute, please go ahead. I’m not interested into fixing this issue. |
So what kind of issue is here? 🤔 |
It’s an issue with your environment. We already talked about that. |
Only now you've mentioned about issue with my env and still you did not shared details about what you've found. |
I did not found more information. Here is what I suggest you to do: |
Again .. it is really not possible to patch anything if it is unknown cause and you are not even trying to help understand what could be the cause. |
If you don’t want to understand what I’m saying it’s your problem. I’m not going to spend more time answering your non-constructive messages. We’re done here. |
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulesLooks like one unit cannot find
pydoctor
🤔Here is pytest output:
Here is list of installed modules in build env
The text was updated successfully, but these errors were encountered: