Skip to content

fix(ci): route hash timing test to performance lane - #1824

Merged
mldangelo-oai merged 3 commits into
mainfrom
fix/ci-route-hash-performance-test
Aug 29, 2026
Merged

fix(ci): route hash timing test to performance lane#1824
mldangelo-oai merged 3 commits into
mainfrom
fix/ci-route-hash-performance-test

Conversation

@mldangelo-oai

Copy link
Copy Markdown
Contributor

Summary

  • Route the wall-clock hash-generation benchmark to the existing performance category instead of running its hard two-second assertion in parallel Windows/Linux fast-test shards.
  • Keep the benchmark enforced by the dedicated single-process Nightly performance lane and add a failing-first regression that prevents it from silently returning to correctness lanes.

Reproduction

PR #1817's Windows fast-test job failed after 19,738 passing tests because test_hash_generation_performance took 2.209 seconds under pytest-xdist and asserted a two-second limit: https://github.com/promptfoo/modelaudit/actions/runs/32933707417/job/98070818332.

Before this change, the new marker regression fails, the benchmark is collected by -m 'not slow and not integration and not performance', and -m performance deselects it. After this change, fast and Nightly correctness selections exclude the benchmark, while the serial performance lane selects and passes it.

Verification

  • New failing-first marker regression: failed before, passed after.
  • CI-equivalent four-worker hashing, Nightly, workflow, and utility suites: 142 passed.
  • Focused serial fast-lane suites: 50 passed, 1 performance test deselected.
  • Dedicated serial performance selection: 1 passed, 75 correctly deselected.
  • Repository-wide Ruff lint: passed.
  • Repository-wide Ruff formatting: 424 files passed.
  • Changed-file mypy: passed.

The broad local suite excludes two pre-existing macOS-only baselines: a cache-hit regression already fixed by #1821 (the same test passes on that PR's head) and an invalid-UTF-8 filename case unsupported by the local filesystem. Current default-branch Linux/Windows CI and all 13 jobs in the latest scheduled Nightly are green.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 26, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-29T01:07:59.323441Z 198fe21 Manual request
🔒 Security Review Completed 2026-08-29T01:08:21.388770Z 198fe21 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@mldangelo-oai

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 72123fb2d0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 72123fb2d0

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@mldangelo-oai

Copy link
Copy Markdown
Contributor Author

@codex review

@mldangelo-oai

Copy link
Copy Markdown
Contributor Author

@codex security review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4b4b5b375c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread tests/test_regular_scan_hash.py
@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 4b4b5b375c

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@mldangelo-oai

Copy link
Copy Markdown
Contributor Author

@codex review

@mldangelo-oai

Copy link
Copy Markdown
Contributor Author

@codex security review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: 198fe210a3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 198fe210a3

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@chatgpt-codex-connector

Copy link
Copy Markdown

Security review completed. No security issues were found in this pull request.

Reviewed commit: 198fe210a3

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@codecov-commenter

codecov-commenter commented Aug 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.45%. Comparing base (56417b8) to head (198fe21).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1824   +/-   ##
=======================================
  Coverage   76.45%   76.45%           
=======================================
  Files         217      217           
  Lines      117014   117014           
  Branches    27624    27624           
=======================================
  Hits        89461    89461           
  Misses      20093    20093           
  Partials     7460     7460           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mldangelo-oai
mldangelo-oai merged commit b4c10f2 into main Aug 29, 2026
43 checks passed
@mldangelo-oai
mldangelo-oai deleted the fix/ci-route-hash-performance-test branch August 29, 2026 01:34
@github-actions github-actions Bot mentioned this pull request Aug 28, 2026
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