[CI] PyPy tests failing lately and it is difficult to identify the root cause
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
I first noticed this behaviour when reverting the deprecations introduced in v78.0.0.
But lately we have seen PyPy failing in what seems to be unrelated issues.
Example extracted from #4931:
We can see an error in test_setupcfg.py:488 which does not really have a good explanation.
In the setuptools.tests.config.test_setupcfg:TestOptions.test_basic function, we use the fake_env, but by itself it does not add any classifier. So we have a warning about classifiers without having specified any classifier?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PyPy CI failure at test_setupcfg.py:488 and the TestOptions.test_basic test, then inspect how fake_env is used there. Compare the failure with the example from #4931 and trace why a classifier warning appears without a classifier. Done means the root cause is reproducible and the PyPy failure becomes explainable or diagnosable in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100