Open jaraco opened 7 months ago
What's new in pytest 8.2 that would trigger this behavior?
I somewhat painstakingly bisected this by using your act
command and adjusting
diff --git i/pyproject.toml w/pyproject.toml
index ebdbf83..1fbe042 100644
--- i/pyproject.toml
+++ w/pyproject.toml
@@ -30,7 +30,7 @@ Homepage = "https://github.com/jaraco/jaraco.xonsh"
[project.optional-dependencies]
testing = [
# upstream
- "pytest >= 6, != 8.1.1",
+ "pytest @ git+https://github.com/pytest-dev/pytest@17fc20af78d0c7b739806c4e461d2c9b8c30ceeb",
"pytest-checkdocs >= 2.4",
"pytest-cov",
"pytest-mypy",
accordingly.
This points me to 99890636bfd9bb156655050f22f1df47e74ac3f6, see:
This issue is perhaps one of the weirdest and most obscure I've seen. My investigation began in jaraco/jaraco.xonsh#1. The summary is this:
docs/conf.py
, something outside the call stack attempts toimport jaraco.xonsh.docs
, even thoughjaraco.xonsh
is a module anddocs
is a sibling ofjaraco
.jaraco.xonsh
might not be problematic except:jaraco.xonsh
module hasn't been collected or tested (in earlier runs or with pytest 8.2 when it passes locally).As you might imagine, creating a minimal example is near impossible given the peculiarities of this scenario. The jaraco.xonsh project is nearly a minimal example in itself. The easiest way to replicate the issue is to clone the project at 249226010f9c9e5490dab851947efba2dceecb63, install act, and run the command in https://github.com/jaraco/jaraco.xonsh/issues/1#issuecomment-2084576106.
Questions for which I'm hoping to find answers:
jaraco.xonsh.docs
and why doesn't it show up in the stack trace?