Skip to content

Fix modern ZAP benchmark runner kill - #802

Closed
preetkaran20 with Copilot wants to merge 2 commits into
masterfrom
copilot/fix-zap-benchmark-job
Closed

preetkaran20 with Copilot wants to merge 2 commits into
masterfrom
copilot/fix-zap-benchmark-job

Conversation

Copilot AI commented Sep 18, 2026 •

Copy link
Copy Markdown

The ZAP Benchmark (modern) GitHub Actions job was failing because the ZAP container was killed with exit code 137 during the AJAX spider phase. The modern automation plan was launching too many headless browsers for the hosted runner.

  • ZAP automation
    • Reduced modern AJAX spider concurrency from 30 to 2 browsers to keep the scan within runner resource limits.
- type: spiderAjax
  parameters:
    numberOfBrowsers: 2
  • Regression guard
    • Added a focused pytest check that prevents the modern AJAX spider browser count from being raised above the CI-safe limit.

@coderabbitai

coderabbitai Bot commented Sep 18, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: fb110481-30b6-47c6-96e0-f8108d18b0c6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Co-authored-by: preetkaran20 <13570884+preetkaran20@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix failing GitHub Actions job ZAP Benchmark (modern) Fix modern ZAP benchmark runner kill Sep 18, 2026
Copilot AI requested a review from preetkaran20 September 18, 2026 22:01
@github-actions

Copy link
Copy Markdown
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants