Closed icemac closed 3 years ago
@icemac thanks for creating this Pull Request and help improve Plone!
To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.
Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:
@jenkins-plone-org please run jobs
With this simple comment all the jobs will be started automatically.
Happy hacking!
@jenkins-plone-org please run jobs
I see no need for a change log entry for such a minor fix in the tests.
I ran tox
locally on Python 3.8 and do not see the ResourceWarning
any more.
@icemac thanks for creating this Pull Request and help improve Plone!
To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.
Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:
@jenkins-plone-org please run jobs
With this simple comment all the jobs will be started automatically.
Happy hacking!
I am agreed that no changelog entry is needed. And all Jenkins tests passed, but the package is not tested there.
Locally, tox -e py39
fails, but that is because it tries to install Zope 4. The GitHub Actions have been setup to do this correctly. Should be doable to fix tox.ini
, but that is not for this PR.
Actions are not triggered yet. I have triggered them manually now for this branch. Let's see. Can be merged if they are green.
The actions are green, I merge.
Fixes #176