Use an async checkpointer to initialize JDI in tests #1170
+13
−13
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.
Description
According to this logic we only initialize the jax distributed system for an async checkpointer, but it looks like sometime recently in orbax this is needed even for a sync checkpointer. We should modify this logic but it may break some single host or pathways use cases which don't need the distributed system. A short term fix is to use an async checkpointer so that the jax distributed system is broken, e.g. for the end_to_end tests b/389730949
Tests
Ran gemma step 2 locally
Checklist
Before submitting this PR, please make sure (put X in square brackets):