[Behat] Introduce Bad Gateway Context#17877
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
❌ Preview Environment deleted from BunnyshellAvailable commands:
|
015ab7b to
de4dc79
Compare
Sometimes, there’s an issue in the CI pipeline—particularly with the Chromedriver build when running on PHP 8.2. You may recall that we previously struggled to run Behat tests locally with PHP 8.2, and upgrading to 8.3 resolved the issue. Unfortunately, we can’t eliminate this combination from the testing flow entirely, but we can at least make it more reliable.
This proposed change aims to improve the developer experience by short-circuiting the execution of the JS job early if a 502 error occurs. While it doesn’t fix the root cause, it does improve the feedback loop.
BadRequestContext service in action:

Another example:
