Move grace download to separate step

[jan-janssen]

Summary by CodeRabbit

• Chores

  • Reorganized our automated workflow to ensure necessary resources are prepared in the correct sequence before tests run, thereby enhancing overall build reliability.

• Tests

  • Adjusted the order of test execution to better manage dependencies, leading to a more robust and efficient validation process.

These improvements help streamline our release process and contribute to more consistent, reliable builds.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the workflow defined in .github/workflows/pipeline.yml by reorganizing the job sequence. The original "Test" job is replaced by a new "Download Grace" job, which downloads and extracts a model tarball from a GitHub repository. A new "Test" job is introduced afterward to install necessary dependencies and execute GRACE-specific unit tests. This reordering ensures that the model is available before testing begins.

Changes

File	Change Summary
.github/workflows/pipeline.yml	Replaced the original "Test" job with "Download Grace" (handles model download, extraction, and cleanup) and added a new "Test" job (installs packages and runs tests)

Sequence Diagram(s)

sequenceDiagram
    participant W as Workflow
    participant DG as "Download Grace Job"
    participant T as "Test Job"
    
    W->>DG: Trigger Download Grace job
    DG-->>W: Download, extract, and cleanup
    W->>T: Trigger Test job
    T-->>W: Install dependencies and run tests

Loading

Possibly related PRs

• Grace use standard dependencies #429: Introduced workflow modifications to streamline the model download process in the pipeline.
• Disable Grace #427: Adjusted GRACE-related testing by disabling an earlier job; relates through the reordering and refactoring of the workflow.

Poem

I'm a rabbit, hopping in code's soft light,
With a new workflow to keep our steps just right.
"Download Grace" fetches the model with flair,
While tests follow smoothly, floating in the air.
Hop along, dear devs, for changes make us smile! 🐰✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6a44626 and 3b643ec.

📒 Files selected for processing (1)

• .github/workflows/pipeline.yml (2 hunks)

---

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

• 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.07%. Comparing base (6a44626) to head (3b643ec).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #438   +/-   ##
=======================================
  Coverage   85.07%   85.07%           
=======================================
  Files          42       42           
  Lines        2546     2546           
=======================================
  Hits         2166     2166           
  Misses        380      380           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.