perf: run TestSuiteGate pytest from project root with correct interpr…#145
perf: run TestSuiteGate pytest from project root with correct interpr…#145shrutu0929 wants to merge 2 commits intoRefactron-ai:mainfrom
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 6 minutes and 58 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
1 participant
solve #141
The recent commit optimizes the internal test runner logic by ensuring TestSuiteGate correctly initiates pytest subprocesses. We transitioned the execution pipeline away from hardcoded "python3" strings to seamlessly utilize the native sys.executable, which inherently forces the subprocess to inherit the exact host environment, resolving potential mismatches with virtual environments or system Python installations. Additionally, instead of defaulting the execution working directory (cwd) contextually to the parent folder of whatever file was changed, the engine now dynamically detects and elevates the execution path to the base project_root or search_root. This crucial adjustment ensures that global configurations—such as pytest.ini, conftest.py, nested tool.pytest logic inside pyproject.toml, and native PYTHONPATH parameters—are successfully discovered and loaded correctly during the initial collection phase, greatly improving execution reliability across diverse repository architectures.