Skip to content

~95% on SimpleQA (e.g. Qwen3.6-27B on a 3090). Supports all local and cloud LLMs (llama.cpp, Ollama, Google, ...). 10+ search engines - arXiv, PubMed, your private documents. Everything Local & Encrypted.

ci: raise the security-tests timeout to 40 minutes (#7376)

LearningCircuita55233d3bd68
diff --git a/.github/workflows/security-tests.yml b/.github/workflows/security-tests.yml
index 90a689a71f..60425b262f 100644
--- a/.github/workflows/security-tests.yml
+++ b/.github/workflows/security-tests.yml
@@ -9,7 +9,7 @@ permissions: {} # Minimal top-level for OSSF Scorecard
jobs:
security-tests:
runs-on: ubuntu-latest
- timeout-minutes: 25
+ timeout-minutes: 40
permissions:
contents: read
security-events: write # Required for uploading SARIF results to Code Scanning
@@ -166,9 +166,9 @@ jobs:
bandit-results.sarif
# Real nginx + production uvicorn login regressions (#5787, #6442).
- # A separate job rather than a step of security-tests: that job already
- # uses ~22 of its 25 minutes on main (17 min of which is the parallel
- # suite), so a trailing step would push a passing run past its timeout.
+ # A separate job rather than a step of security-tests: that job's parallel
+ # suite alone has grown past 20 minutes on main (its timeout is 40), so a
+ # trailing step would push a passing run past its timeout.
# Both jobs live in this reusable workflow, so release-gate.yml's
# `security-tests` caller job fails if either of them fails.
proxy-login-tests: