The PIP testing is fragile, various hacks are included already. It has
been failing persistently in the CI and locally on OpenSuSE. Since
general PIP use requires network access, it is better done during CI
anyway.
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
tests/test-install.t | ||
---|---|---|
187 | It would be nice to keep the py3 part if it's not failing on CI and OpenSUSE. |
Comment Actions
The strange thing is that I see the Python 2 failures on the Heptapod CI and the Python 3 failures on OpenSuSE. Both with the system Python and the pkgsrc one in the later case. IMO if we want to do testing for PIP, it should be on the CI only.
It would be nice to keep the py3 part if it's not failing on CI and OpenSUSE.