Skip to content

Fix CI pipeline missing torch dependency by running pytest through sys.executable#5

Open
Vishal-sys-code wants to merge 1 commit into
mainfrom
fix-ci-pytest-executable-9021092358631868550
Open

Fix CI pipeline missing torch dependency by running pytest through sys.executable#5
Vishal-sys-code wants to merge 1 commit into
mainfrom
fix-ci-pytest-executable-9021092358631868550

Conversation

@Vishal-sys-code

Copy link
Copy Markdown
Owner

This commit fixes the failing VLA integration tests in CI.

The root cause was that ci/run_pipeline.py was calling pytest directly via subprocess. This resulted in an isolated pytest installation (from pipx or a global install) running instead of using the environment where dependencies like torch were installed. By explicitly running [sys.executable, "-m", "pytest"], we ensure that tests run in the active Python environment with all required packages available.


PR created automatically by Jules for task 9021092358631868550 started by @Vishal-sys-code

This commit changes the `subprocess.run` call in `ci/run_pipeline.py` from `["pytest", ...]` to `[sys.executable, "-m", "pytest", ...]`.

This ensures that `pytest` is executed within the same Python environment that is currently running the pipeline. This resolves a `ModuleNotFoundError: No module named 'torch'` caused by the pipeline calling an isolated global `pytest` installation that did not have access to the dependencies installed for the project.

Co-authored-by: Vishal-sys-code <68536727+Vishal-sys-code@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel

vercel Bot commented Apr 7, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
variational-linear-attention Ready Ready Preview, Comment Apr 7, 2026 4:24am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant