Repository navigation
Fix modern ZAP benchmark runner kill - #802
preetkaran20 with Copilot wants to merge 2 commits into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Co-authored-by: preetkaran20 <13570884+preetkaran20@users.noreply.github.com>
|
This PR has had no activity for 30 days, so it's been marked stale. If you're still working on it, push a commit or leave a comment and this label will clear. Otherwise it'll close automatically in 60 days — no hard feelings, and you (or anyone else) are welcome to reopen or resubmit against current main whenever you're ready. |
The
ZAP Benchmark (modern)GitHub Actions job was failing because the ZAP container was killed with exit code137during the AJAX spider phase. The modern automation plan was launching too many headless browsers for the hosted runner.30to2browsers to keep the scan within runner resource limits.