@enough-analyst-54434 if I start with a clean cache

rm -rf .pants.d/

run a test goal with the error in pytest, update pants.ini to pin the old version. Then run pants test goal again with

--cache-test-pytest-ignore

it throws the error.

Ack - did you see I filed a bug?

no sorry

Ah - no worries: https://github.com/pantsbuild/pants/issues/7239

@jolly-memory-78838 I hit the same issue and rolled my own version of pytest to work around the issue for the moment.

jvenus-signal-mbp13:pytest jvenus$ git diff
diff --git a/setup.py b/setup.py
index 908abb18..bb91fb35 100644
--- a/setup.py
+++ b/setup.py
@@ -63,7 +63,7 @@ def main():
         "six>=1.10.0",
         "setuptools",
         "attrs>=17.4.0",
-        "more-itertools>=4.0.0",
+        "more-itertools==5.0.0",
         "atomicwrites>=1.0",
     ]

then I pinned the version in pants.ini

diff --git a/pants.ini b/pants.ini
index 8bd5ad66..a74ace51 100644
--- a/pants.ini
+++ b/pants.ini
@@ -193,6 +193,13 @@ options: [
 [scala-platform]
 version: 2.12

+[pytest]
+requirements: pytest==3.6.5
+timeout_requirements: pytest-timeout>=1.2,<1.3
+cov_requirements: pytest-cov>=2.4,<2.5
+unittest2_requirements: unittest2>=0.6.0,<=1.9.0
+