Skip to content

Stabilize release CI performance tests#370

Merged
ModerRAS merged 1 commit into
masterfrom
fix/release-ci-performance-tests
Jul 26, 2026
Merged

Stabilize release CI performance tests#370
ModerRAS merged 1 commit into
masterfrom
fix/release-ci-performance-tests

Conversation

@ModerRAS

@ModerRAS ModerRAS commented Jul 26, 2026

Copy link
Copy Markdown
Owner

Summary

  • Classify VectorPerformanceTests as performance benchmarks.
  • Exclude environment-sensitive benchmarks from PR and release CI validation.
  • Retain all functional vector tests in CI.

Validation

  • Release build succeeded.
  • Non-performance test selection: 410 passed, 1 skipped, 0 failed.
  • Category=Performance discovers five vector benchmark tests.

Summary by CodeRabbit

  • Tests
    • Categorized vector performance tests as “Performance.”
    • Updated automated validation runs to exclude performance tests from standard test execution.

@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0a6fc2ef-6f06-4fac-97dc-45977f9e9f29

📥 Commits

Reviewing files that changed from the base of the PR and between 09c0ede and 8c74420.

📒 Files selected for processing (3)
  • .github/workflows/pr.yml
  • .github/workflows/push.yml
  • TelegramSearchBot.Test/Service/Vector/VectorPerformanceTests.cs

📝 Walkthrough

Walkthrough

The vector performance test suite is tagged with the Performance category. Push validation excludes that category, while the pull-request test command retains its existing arguments with a line placement update.

Changes

Performance test filtering

Layer / File(s) Summary
Categorize vector performance tests
TelegramSearchBot.Test/Service/Vector/VectorPerformanceTests.cs
Adds the xUnit Performance trait to the vector performance test class.
Apply CI test filtering
.github/workflows/push.yml, .github/workflows/pr.yml
Excludes Performance tests from push validation; the pull-request test command’s placement changes without altering its arguments.

Estimated code review effort: 1 (Trivial) | ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the main change: CI now excludes performance tests and the benchmark suite is marked as Performance.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/release-ci-performance-tests

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.

@github-actions

Copy link
Copy Markdown
Contributor

PR Check Report

Summary

Test Results

Platform Status Details
Ubuntu Passed Tests passed, artifacts uploaded
Windows Passed Tests passed, artifacts uploaded

Code Quality

  • Code formatting check
  • Security vulnerability scan
  • Dependency analysis
  • Code coverage collection

Test Artifacts

  • Test results artifacts count: 2
  • Code coverage uploaded to Codecov

Links


This report is auto-generated by GitHub Actions

@ModerRAS
ModerRAS merged commit 9ced0fa into master Jul 26, 2026
5 checks passed
@ModerRAS
ModerRAS deleted the fix/release-ci-performance-tests branch July 26, 2026 01:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant