-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
3.8.0: pytest is failing in ::project
unit
#9
Comments
It appears that in your environment, when pytest-checkdocs invokes:
Which results in an exception. Unfortunately, the exception is unclear from the output. It fails to create a build environment in order to compute the metadata. I'd suggest to try to replicate the error using pep517 only. If you can create a Dockerfile that replicates the issue, I can probably inspect more deeply. I don't believe this project is doing anything special compared to other projects I maintain, so I'm surprised the issue is only happening with this project in particular. To work around the issue, you can probably disable the checkdocs plugin by passing |
Please have look one more time on top of this ticket.
I'm not using docker and ano go related software as it popents seriouse security risk (please look on rate of CVEs in golang; docker implemeted in python is no longer maintained). Package Version
----------------------------- -----------------
alabaster 0.7.12
attrs 22.1.0.dev0
Babel 2.10.2
Brlapi 0.8.3
build 0.8.0
charset-normalizer 2.1.0
codespell 2.1.0
cycler 0.11.0
distro 1.7.0
docutils 0.17.1
extras 1.0.0
fixtures 4.0.0
fonttools 4.33.3
gpg 1.17.1-unknown
idna 3.3
imagesize 1.4.1
importlib-metadata 4.12.0
importlib-resources 5.8.0
iniconfig 1.1.1
jaraco.context 4.1.1
jaraco.functools 3.5.0
jaraco.packaging 9.0.0
Jinja2 3.1.1
kiwisolver 1.4.3
libcomps 0.1.18
louis 3.22.0
MarkupSafe 2.1.1
matplotlib 3.5.2
more-itertools 8.13.0
numpy 1.23.0
olefile 0.46
packaging 21.3
pbr 5.8.1
pep517 0.12.0
Pillow 9.2.0
pip 22.0.4
pluggy 1.0.0
py 1.11.0
Pygments 2.12.0
PyGObject 3.42.1
pyparsing 3.0.9
pyrsistent 0.18.1
pytest 7.1.2
python-dateutil 2.8.2
pytz 2022.1
requests 2.28.1
rpm 4.17.0
rst.linker 2.3.0
setuptools 63.1.0
setuptools-scm 7.0.4
six 1.16.0
snowballstemmer 2.2.0
Sphinx 5.0.2
sphinxcontrib-applehelp 1.0.2.dev20220410
sphinxcontrib-devhelp 1.0.2.dev20220410
sphinxcontrib-htmlhelp 2.0.0
sphinxcontrib-jsmath 1.0.1.dev20220704
sphinxcontrib-qthelp 1.0.3.dev20220704
sphinxcontrib-serializinghtml 1.1.5
testtools 2.5.0
tomli 2.0.1
traitlets 5.3.0
typing_extensions 4.2.0
urllib3 1.26.9
wheel 0.37.1
zipp 3.8.0
Is ti not easier to fix that issue? |
The problem is that I don't have a way to replicate the issue. Tests pass for me. Moreover, this project is using the same technique of pytest-checkdocs. I can't think of any reason why this project should have trouble but the dozens of others I maintain do not. |
I did try replicating the issue by using pip to install packages to system Python 3.10 on Ubuntu 20.04, but the tests still run. I need help replicating the issue. If not a dockerfile, can you provide a script that replicates the issue on a clean OS image? |
This issue is possible to solve by:
|
The
Someone needs to implement a mechanism for offline builds to support building metadata. |
I'm trying to package 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 modulesHere is pytest output:
I'm going add that unit in my build procedure to --deselet list.
The text was updated successfully, but these errors were encountered: