Remove PyTorch/Pyro-PPL and switch to CPU-only JAX on GitHub-hosted runners#692
Closed
Remove PyTorch/Pyro-PPL and switch to CPU-only JAX on GitHub-hosted runners#692
Conversation
Create ~/.config/netlify directory with proper permissions before running Netlify CLI to prevent EACCES errors. This issue occurs because the CLI is installed globally with sudo but runs as the regular user, requiring write access to the config directory.
Resolved conflicts in .github/workflows/ci.yml by keeping the CPU-only JAX configuration and GitHub-hosted runner setup from this branch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR removes PyTorch and Pyro-PPL dependencies and switches from RunsOn GPU instances to GitHub-hosted runners with CPU-only JAX.
Changes:
runs-onGPU instances (g4dn.2xlarge) to GitHub-hosted runners (ubuntu-latest)pip install -U jaxThis approach avoids CUDA driver compatibility issues by running JAX in CPU mode.