hotfix-nigthly-1

[nirtal85]

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

Summary by CodeRabbit

• New Features

  • Enhanced nightly regression tests with a new setup for dynamic test matrix parallelism.
  • Introduced a new job, merge-reports, to aggregate Allure test results.
  • Expanded input options for specifying test parallelism.

• Documentation

  • Streamlined comments in the dev workflow for clarity.

[coderabbitai]

Walkthrough

The recent changes enhance GitHub Actions workflows by streamlining documentation in the devRun.yml file, while significantly restructuring the nightly.yml file. A new job setup allows for dynamic test matrix generation, improving parallel execution and flexibility. This update also includes a report merging feature for Allure results, providing better insights post-testing. Overall, these modifications optimize the testing workflow and improve functionality.

Changes

Files	Change Summary
.github/workflows/devRun.yml	Reduced comments; no changes to functionality or logic.
.github/workflows/nightly.yml	Introduced setup-matrix job for dynamic test matrix generation; renamed nightly to nightly-test; added merge-reports job; updated input parameters and test execution steps.

Poem

In the meadow of code, where bunnies hop,
We've spruced up our workflows, they’ll never stop!
With tests now running in parallel delight,
We'll gather the reports, shining and bright.
So here’s to the changes, let’s give a cheer,
For smoother paths ahead, it’s a joyful year! 🐇✨

---

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5a3ac26 and b4a0a97.

Files selected for processing (2)

• .github/workflows/devRun.yml (1 hunks)
• .github/workflows/nightly.yml (3 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/devRun.yml

Additional comments not posted (6)

.github/workflows/nightly.yml (6)

12-17: LGTM! Addition of parallelism input parameter.

The new parallelism input parameter enhances the flexibility of the workflow by allowing users to specify the number of machines for parallel test execution.

---

20-30: LGTM! Addition of setup-matrix job.

The setup-matrix job dynamically generates a test matrix based on the parallelism input, improving the flexibility and scalability of the testing process.

---

Line range hint 31-67:
LGTM! Updates to nightly-test job.

The updates to the nightly-test job ensure that it leverages the dynamically generated matrix for parallel test execution. The steps have been updated to reflect these changes.

---

Line range hint 68-98:
LGTM! Addition of merge-reports job.

The merge-reports job aggregates Allure test results from all test runs and generates a report, ensuring that test results are compiled and accessible.

---

63-66: LGTM! Usage of parallelism in test execution command.

The usage of parallelism in the test execution command ensures that tests are distributed across multiple machines as specified by the user.

---

Line range hint 73-98:
LGTM! Steps in merge-reports job.

The steps in the merge-reports job are well-defined and ensure that Allure test results are merged, Git information is linked, reports are generated, and reports are deployed to GitHub Pages.