Skip to content

Conversation

@mauritsvanrees
Copy link
Member

See for example this failure on Jenkins. The test created two content items with Subjects, and querying for all items without a specific Subject. This used to return 1 item. But now it returns 2, because the Plone Site object is also returned, which has no Subject set. This object used to be ignored in the catalog. See zopefoundation/Products.ZCatalog#148

What is a bit strange, is that the 'not' query does not return any results when I run it at the beginning of this test, so before any item with this Subject has been set. That might be a problem in ZCatalog still.

Note that the GitHub Actions tests will fail because they use an older Products.ZCatalog. So I am making a PR in buildout.coredev to update the pin and make a checkouts of this PR branch. If that is green, I can merge this PR, and update the ZCatalog pin in the coredev buildout and dist.plone.org.

See for example this [failure on Jenkins](https://jenkins.plone.org/job/pull-request-6.2-3.13/426/testReport/junit/plone.app.querystring.tests.testQueryBuilder/TestQuerybuilder/testMakeQueryWithMultipleSubjectNot/).  The test created two content items with Subjects, and querying for all items without a specific Subject.  This used to return 1 item.  But now it returns 2, because the Plone Site object is also returned, which has no Subject set.  This object used to be ignored in the catalog.  See zopefoundation/Products.ZCatalog#148

What is a bit strange, is that the 'not' query does not return any results when I run it at the beginning of this test, so before any item with this Subject has been set.  That might be a problem in ZCatalog still.
@mister-roboto
Copy link

@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!

@mauritsvanrees
Copy link
Member Author

The coredev PR is green. I have pushed Products.ZCatalog 7.2.1 to dist.plone.org/release/6.2-dev and restarted the jobs in the current PR and they are green to. So I merge this one and push the new ZCatalog version to coredev.

@mauritsvanrees mauritsvanrees merged commit cd582af into master Nov 21, 2025
14 of 19 checks passed
@mauritsvanrees mauritsvanrees deleted the maurits-tests-newer-zcatalog branch November 21, 2025 16:26
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

Successfully merging this pull request may close these issues.

3 participants