Conversation
Contributor
|
Thanks a lot, @thomasw21 |
Contributor
|
codecarbon is not ready mlco2/codecarbon#238 that's why I was trying to disable it in the slurm script. |
Contributor
|
Got a chance to test it, your fix is perfect, @thomasw21! Thank you! |
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.
We've noticed that 13B training crashed.
The logs suggest that it's linked to the new carbon feature:
I'm pretty sure it's because we don't check the value of
args.codecarbon_dir, it defaults to None using the argument parser.Instead we need to check that that value is not None.
I don't think the fix is urgent since we'll be running with the option activated from now on. (though it might impact smaller experiments)