Page MenuHomePhabricator

tests: drop pip test on the client
AbandonedPublic

Authored by joerg.sonnenberger on Jan 30 2021, 8:05 AM.

Details

Reviewers
None
Group Reviewers
hg-reviewers
Summary

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.

Diff Detail

Repository
rHG Mercurial
Branch
default
Lint
No Linters Available
Unit
No Unit Test Coverage

Event Timeline

baymax updated this revision to Diff 25396.Jan 30 2021, 10:33 AM

โœ… refresh by Heptapod after a successful CI run (๐Ÿ™ ๐Ÿ’š)

pulkit added a subscriber: pulkit.Jan 31 2021, 2:59 PM
pulkit added inline comments.
tests/test-install.t
187

It would be nice to keep the py3 part if it's not failing on CI and OpenSUSE.

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.

Superseded by D9950