3.0.4: pytest is failing in some units
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 419
- PR merge metrics
- No merged PRs in 30d
Description
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`
- because I'm calling `build` with `--no-isolation` I'm using during all processes only locally installed modules
- install .whl file in using 'installer` module
- run pytest with $PYTHONPATH pointing to sitearch and sitelib inside
- build is performed in env which is *`cut off from access to the public network`* (pytest is executed with `-m "not network"`)
List of installed modules in build env:
```console
Package Version
----------------------------- -------
alabaster 0.7.13
Babel 2.13.1
blinker 1.6.2
build 1.0.3
cairocffi 1.6.1
CairoSVG 2.7.1
cffi 1.16.0
charset-normalizer 3.3.2
click 8.1.7
cppclean 0.13
cssselect 1.2.0
cssselect2 0.7.0
defusedxml 0.7.1
distro 1.8.0
dnf 4.18.1
docutils 0.20.1
exceptiongroup 1.1.3
Flask 3.0.0
gpg 1.23.0
idna 3.6
imagesize 1.4.1
importlib-metadata 7.0.0
iniconfig 2.0.0
installer 0.7.0
itsdangerous 2.1.2
Jinja2 3.1.2
libdnf 0.72.0
lxml 4.9.3
MarkupSafe 2.1.3
olefile 0.46
packaging 23.2
Pillow 10.1.0
pluggy 1.3.0
ply 3.11
pycparser 2.21
Pygments 2.17.2
pyproject_hooks 1.0.0
pyquery 2.0.0
pytest 7.4.3
python-dateutil 2.8.2
pytz 2023.3
requests 2.31.0
setuptools 69.0.2
six 1.16.0
snowballstemmer 2.2.0
Sphinx 7.1.2
sphinx-rtd-theme 1.2.2
sphinxcontrib-applehelp 1.0.4
sphinxcontrib-devhelp 1.0.5
sphinxcontrib-htmlhelp 2.0.4
sphinxcontrib-jquery 4.1
sphinxcontrib-jsmath 1.0.1
sphinxcontrib-qthelp 1.0.3
sphinxcontrib-serializinghtml 1.1.9
tinycss2 1.2.1
tomli 2.0.1
urllib3 1.26.18
webencodings 0.5.1
Werkzeug 3.0.0
wheel 0.42.0
zipp 3.17.0
```
Contributor guide
Research direction
No failing unit, traceback, or source file is named. Reproduce the PEP517 build and wheel installation with `python3 -sBm build -w --no-isolation`, the listed local dependencies, and `pytest -m "not network"` with PYTHONPATH set to the install prefix. Done means the failing tests are identified and pass in the offline, non-root installation scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100