Draft
Conversation
alinelena
force-pushed
the
tests_cuda
branch
2 times, most recently
from
1e3a424 to
05c5f78
Compare
Member
Author
|
needs !689 to get in |
Member
|
I think this is based off of #689, so we should probably merge that first and rebase. Tests are looking better re-running now. I'm wondering if the error was from mlco2/codecarbon#1122, which has been fixed as of a release yesterday. It says it was a warning, but perhaps the underlying Looks like we need to loosen the dispersion comparison slightly too. |
alinelena
force-pushed
the
tests_cuda
branch
2 times, most recently
from
55cfbf9 to
b279a69
Compare
alinelena
commented
Apr 10, 2026
Co-authored-by: Elliott Kasoar <[email protected]>
Co-authored-by: Elliott Kasoar <[email protected]>
Co-authored-by: Elliott Kasoar <[email protected]>
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
2 participants
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.
adding posibility some of the tests to run on cuda. create a workflow for them.. shall we force the other tests to run cpu only?