ci: use INFO loglevel in the Redis deploy jobs#893
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates two Redis-hosted Nextcloud CI jobs in .github/workflows/tests-deploy.yml to set Nextcloud's system 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
c48fefe to
873f58e
Compare
Signed-off-by: Oleksander Piskun <oleksandr2088@icloud.com>
873f58e to
dbb95ca
Compare
Since June 5 the two Redis jobs failed every run: occ crashes during setup with "Maximum call stack size reached during compilation" (or a segfault if the PHP 8.3 stack check is disabled). The root cause is on current server master since nextcloud/server#59002: the deprecated RedisFactory alias logs a deprecation at debug level, writing that entry resolves IRequest in the middle of DI construction, and the container recurses until the stack overflows. The crash needs a Redis memcache plus loglevel 0, and INFO level is fine for the CI anyway, so use that in the Redis jobs.