Default use_cache=False
in eval harness integration
#774
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.
When running the eval-harness via GPT-NeoX using more than 1 GPU, evals would fail by default unless setting
use_cache=False
with an error like the following:This PR just defaults the caching to False, to avoid this. I think we want the cache off anyway because the naming of the cache doesn't adequately distinguish between different eval steps(?) and so evals would mistakenly read from prior steps' cache.