Closed mauritsvanrees closed 1 year ago
@mauritsvanrees thanks for creating this Pull Request and helping to improve Plone!
TL;DR: Finish pushing changes, pass all other checks, then paste a comment:
@jenkins-plone-org please run jobs
To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.
Happy hacking!
I am testing this on Jenkins together with https://github.com/plone/plone.dexterity/pull/189.
This is for the branch used in Plone 5.2. Backported from version 2.0, specifically PR #27 which was needed to get the dexterity site root working. I already commented there two years ago that I wondered if this would be safe for 5.2 as well.
This fixes test failures on Plone 5.2 Python 3 when used together with https://github.com/plone/plone.dexterity/pull/189, which is a backport of a memory leak fix. Failures are like this:
The test failures are mostly in
plone.autoform
and inplone.app.registry
, but strangely you do not get the error when you run only the tests for one of those packages. You really need to run the entire Plone test suite (bin/test
in coredev, without options). So there is likely some test leakage. See all failures on Jenkins.Python 2 does not have this problem: sorting on Python 3 is handled differently. On Python 2:
On Python 3: