Development: Fix regex in GitHub test action to only find truly failed test cases

[maximiliansoelch]

Checklist

General

• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

Currently, the GH test action always fails due to the regex also finding false positives:

Description

This PR updates the regex and appends an end-of-string check ($) to it.

Steps for Testing

Look into the output of this PR's GH server-test action and confirm that the two false positives from the screenshot above are not shown anymore.

Review Progress

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Summary by CodeRabbit

• Bug Fixes
  • Improved accuracy of test failure detection in CI/CD workflow, reducing false positives in test reporting.
  • Enhanced reliability of output logs by ensuring only legitimate test failures are counted.

[coderabbitai]

Walkthrough

The recent changes enhance the accuracy of test failure detection in GitHub Actions workflows. By refining the regular expressions used in grep commands, the updates ensure that only legitimate test failures are captured, minimizing false positives. This adjustment improves the reliability of test reporting in the CI/CD pipeline across various Spring profiles.

Changes

Files	Change Summary
.github/workflows/test.yml	Improved grep patterns for detecting test failures, ensuring "FAILED" appears at the end of the line to reduce false positives. Applied consistently across different test job configurations.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI/CD Pipeline
    participant Test as Test Runner
    participant Log as Logs

    CI->>Test: Trigger Test Execution
    Test->>Log: Log Test Results
    Log->>CI: Output Logs
    CI->>CI: Check for "Test >.* FAILED$"
    alt If Test Failed
        CI->>CI: Report Failure
    else
        CI->>CI: No Action
    end

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.