-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Test showing the difference #1716
Test showing the difference #1716
Conversation
✅ Deploy Preview for plone-restapi canceled.
|
@sneridagh thanks for creating this Pull Request and helping to improve Plone! TL;DR: Finish pushing changes, pass all other checks, then paste a comment:
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! |
61951e5
to
6e081ff
Compare
@sneridagh @davisagli this issue was fixed in: The test is passing now. |
@wesleybl Then shouldn't we merge the test, to make sure there isn't a future regression, instead of closing the PR? |
@sneridagh thanks for creating this Pull Request and helping to improve Plone! TL;DR: Finish pushing changes, pass all other checks, then paste a comment:
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! |
@davisagli Okay. I made some fixes. |
@jenkins-plone-org please run jobs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
f7fb7bb
to
13f1d47
Compare
@jenkins-plone-org please run jobs |
@sneridagh @davisagli can you merge this PR please? I think Plone 6.1 is no longer tested with Python 3.8 in Jenkins. |
@wesleybl I updated the repository's branch protection rules so that it requires the Plone 6.1 + Python 3.10 build instead of Python 3.8. |
The test fails right now.