plone
@rules endpoint
@avoinea 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!
Deploy Preview for plone-restapi ready!
| Name | Link |
|---|---|
| Latest commit | 1fc560a5f8c33c20aa8f80883a0828a160c1074b |
| Latest deploy log | https://app.netlify.com/sites/plone-restapi/deploys/63204c0dd037a600085e2dc4 |
| Deploy Preview | https://deploy-preview-1411--plone-restapi.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
As mentionned at the Volto team meeting tuesday 7th, 'we' are aware of the recent testing issues. These are unstable robottests that fail occasionally that crept into core and where a problem with the reporting let the number increase too much before we noticed them. And then it became a situation of always some (and too many) seemingly random tests failing, but it was always a subset.
We're almost back to zero failing tests most of the runs, I manually started the pull-request-6.0-3.8 yesterday evening, which we have modfied locally on jenkins to only run robot tests and with some other tweaks/experiments to improve the overall tests. I'll get back to this PR when we are finished and run the jobs again.
