ci: fix uv cache in CI workflows

[ogabrielluiz]

Eliminate the UV_CACHE_DIR environment variable and the associated cache restoration step from GitHub workflows to streamline the CI process.

The setup-uv action cached with one key but we looked up a different format, causing cache misses.
Example:

cache saved with the key: setup-uv-1-x86_64-unknown-linux-gnu-0.7.9-2b8ee67a007765037fec8b697d12ed35e766c5e388e33f436dac807b058ccc6b

Cache not found for input keys: uv-Linux-2b8ee67a007765037fec8b697d12ed35e766c5e388e33f436dac807b058ccc6b, uv-Linux-2b8ee67a007765037fec8b697d12ed35e766c5e388e33f436dac807b058ccc6b, uv-Linux

Summary by CodeRabbit

• Chores
  • Removed caching steps and related environment variables for uv cache from GitHub Actions workflows and composite actions.
• New Features
  • Added a new "benchmark" test marker to the pytest configuration for improved test categorization.

[coderabbitai]

"""

Walkthrough

This change removes the use of the UV_CACHE_DIR environment variable and the related cache restoration step for the /tmp/.uv-cache directory from several GitHub Actions workflows and a composite action. Additionally, a new pytest marker "benchmark" was added to the pytest configuration. No other workflow steps or logic were modified.

Changes

File(s)	Change Summary
.github/actions/setup-uv/action.yml	Removed the "Restore uv cache" step using actions/cache@v4.
.github/workflows/python_test.yml .github/workflows/store_pytest_durations.yml .github/workflows/typescript_test.yml	Removed UV_CACHE_DIR environment variable from job configurations.
pyproject.toml	Added "benchmark" marker to pytest configuration.

Suggested labels

size:M, ignore-for-release

Suggested reviewers

• edwinjosechittilappilly
  """

---

📜 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 7a44d92 and bb64f1e.

📒 Files selected for processing (1)

• pyproject.toml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• pyproject.toml

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.