Closed jaraco closed 2 weeks ago
On my local machine, I'm able to build from scratch, but a few of the tests fail with the same MinimalDistribution has no attribute entry_points
error. I suspect a release of tox or virtualenv may be implicated.
If I run the tests on a local Linux docker image, I see the same failures I observe on my local mac, but not the build errors I see in CI. So I'm going to focus on fixing those errors and then worry about CI subsequently if it's continuing to fail.
The first failure I encounter occurs during test setup when an sdist is produced.
If I clean the directory then home in on just that test, I see the error emitted in CI:
I see pyproject-hooks was released 12 hours ago, so may be pertinent.
Downgrading to pyproject-hooks!=1.1
works around the failure.
Well, that change fixed things for me locally, but doesn't fix the issue in CI. I wonder what's different about the CI build.
Aah. Setuptools uses a pre-built wheel and sdist and that invocation of pipx doesn't honor the pin. That also explains why CI was seeing the issue earlier, because that invocation of build encounters the issue prior to setting up the test environment.
The remaining failure is one that was exhibited a few days ago. I'll file a separate issue about that.
This issue is still affecting docs builds.
I was unable to replicate the docs build failures with tox -e docs
, so I'm attempting a fix by pushing to main.
As recently as four days ago, tests were passing. A day later, one test (test_license_is_a_string), started failing. Today, the package fails to build/install at all. All of these jobs are on the same commit (0156e248e).