Skip to content

chore: pin pytest and ruff cache paths to avoid out-of-repo writes on windows#620

Merged
sreerevanth merged 2 commits into
sreerevanth:mainfrom
pavsoss:issue-611-pytest-cache
Jul 14, 2026
Merged

chore: pin pytest and ruff cache paths to avoid out-of-repo writes on windows#620
sreerevanth merged 2 commits into
sreerevanth:mainfrom
pavsoss:issue-611-pytest-cache

Conversation

@pavsoss

@pavsoss pavsoss commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Closes #611

This PR addresses the permission errors encountered on Windows where pytest and ruff default to writing their cache/tmp files to the system temporary directory (which often fails on fixture setup).

  • pyproject.toml: Pinned cache_dir for pytest and cache-dir for ruff to strictly use repository-local hidden folders (.pytest_cache and .ruff_cache).
  • pyproject.toml: Appended --basetemp=.pytest-tmp to addopts so Pytest strictly writes temp files inside the repository.
  • .gitignore: Added .pytest-tmp/ to ensure these local temp files never get tracked.

@vercel

vercel Bot commented Jul 12, 2026

Copy link
Copy Markdown

@pavsoss is attempting to deploy a commit to the sreerevanth's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@pavsoss, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e09e8f54-45d1-4989-aae5-1f4e113536ff

📥 Commits

Reviewing files that changed from the base of the PR and between 1d2f313 and 2b6aef6.

📒 Files selected for processing (2)
  • .gitignore
  • pyproject.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit 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

github-actions Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

🧪 PR Test Results

Check Result
Tests (pytest tests/) ✅ success
Lint (ruff check .) ❌ failure
Coverage (agentwatch) 74.69%

Python 3.12 · commit 2b6aef6

@vercel

vercel Bot commented Jul 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
agent-watch Ready Ready Preview, Comment Jul 14, 2026 6:15pm

@sreerevanth sreerevanth merged commit d2980f6 into sreerevanth:main Jul 14, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CHORE] pytest writes its cache and tmp files outside the repo, breaking Windows runs

2 participants