Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tox is broken: couldn't open ...buildout.cfg #52

Closed
jugmac00 opened this issue Mar 3, 2021 · 3 comments
Closed

tox is broken: couldn't open ...buildout.cfg #52

jugmac00 opened this issue Mar 3, 2021 · 3 comments

Comments

@jugmac00
Copy link
Member

jugmac00 commented Mar 3, 2021

Currently I am running tox for all Zope and Plone repos, as the upcoming tox4 release is a complete rewrite and some breaking changes and regressions are expected, see zopefoundation/meta#66

While I noticed an endless setuptools upgrade loop for tox4, tox (3) is broken anyway.

❯ tox -e py38
py38 installed: zc.buildout==2.13.3
py38 run-test-pre: PYTHONHASHSEED='3646606669'
py38 run-test: commands[0] | /home/jugmac00/All/output_zope/zopefoundation/zopetoolkit/.tox/py38/bin/buildout -c /home/jugmac00/All/output_zope/zopefoundation/zopetoolkit/buildout.cfg buildout:directory=/home/jugmac00/All/output_zope/zopefoundation/zopetoolkit/.tox/py38 install test-ztk
Upgraded:
  setuptools version 50.3.0;
restarting.
While:
  Initializing.
Error: Couldn't open /home/jugmac00/All/output_zope/zopefoundation/zopetoolkit/.tox/py38/buildout.cfg
ERROR: InvocationError for command /home/jugmac00/All/output_zope/zopefoundation/zopetoolkit/.tox/py38/bin/buildout -c buildout.cfg buildout:directory=/home/jugmac00/All/output_zope/zopefoundation/zopetoolkit/.tox/py38 install test-ztk (exited with code 1)
_____________________________________________________________________________ summary _____________________________________________________________________________
ERROR:   py38: commands failed

There is still a "test passing" badge from Travis in the readme, although Travis does not work anymore.

The GHA tests are not executed regularly - maybe a weekly run would be good so breakages are spotted early on.

@mauritsvanrees
Copy link
Member

Looks like this is the same failure that I saw when working on a plone.api PR. I pinned zc.buildout and setuptools to prevent an upgrade. Otherwise bin/buildout other/dir/buildout.cfg would start out okay, but then upgrade and restart itself, and complain that buildout.cfg cannot be found in the current directory. I guess this is a bug in the self-upgrade code of buildout.

@jugmac00
Copy link
Member Author

jugmac00 commented Mar 3, 2021

I had the exact same error in plone/plone.memoize#24

I did not try to investigate what's broken for plone.api (on tox4) as there was already an issue plone/plone.api#448

@icemac
Copy link
Member

icemac commented Sep 15, 2023

Fixed somewhere along the way.

@icemac icemac closed this as completed Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants