Use a machine.dev runner to get GPU testing - #22
Merged
Conversation
…with torch/CUDA capabilities.
…correct device. Add device transfer for scattering models and scalers.
Removed 'tenancy=ondemand' from the GPU configuration.
…to machinedotdev_runner
…t enough to not be cancelled.
…rence gets just above the 1.045 number with the non-isothermal dust.
Owner
Author
|
Just a quick note that as currently set up, these tests cost ~40 credits on machine.dev. As $10 = 2000 credits, this is about 40 runs for $10 at current cost. |
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.
GPU runners aren't available at my level of GitHub service, so right now testing happens only on CPU (or when I use GPUs on local machines). This PR is to test using machine.dev to provision GPU runners for the E2E testing to get online GPU testing automatically.