• Resolves: #

Summary

Make SearchBuilderTest less flaky by removing its dependence on a fixed storage id in filecache.

Changes

• use a unique numericStorageId per test run instead of 10000
• defensively clean matching filecache rows in setUp()
• fix addCacheEntry() so storage_mtime is assigned after defaulting mtime

Why

This DB test currently inserts/searches rows in filecache using a hard-coded storage = 10000 and only cleans up in tearDown(). If stale rows exist for that storage, the assertions can pick up unrelated fileids and fail nondeterministically in CI.

Using a unique storage id makes the test self-isolating, and the storage_mtime change fixes a small helper bug where mtime could be read before default initialization.

TODO

• ...

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI