Skip to content
This repository was archived by the owner on Apr 23, 2025. It is now read-only.

Conversation

saeta
Copy link
Contributor

@saeta saeta commented Jul 20, 2020

No description provided.

@saeta saeta requested review from shabalind and ematejska July 20, 2020 21:52
@saeta
Copy link
Contributor Author

saeta commented Jul 20, 2020

Related PR: #640

@shabalind
Copy link
Contributor

Alternative idea: maybe we should just tag 0.1 for swift-benchmark instead of using hashes?

@saeta
Copy link
Contributor Author

saeta commented Jul 21, 2020

I think for going forward, that makes sense. for the S4TF v0.11 release, I think pinning to a specific commit is probably the best, as we need a commit that's not the latest.

@saeta saeta merged commit 522466c into tensorflow-0.11 Jul 21, 2020
@saeta saeta deleted the pin-swift-benchmark-0.11 branch July 21, 2020 15:21
BradLarson added a commit that referenced this pull request Aug 19, 2020
* Pin Swift-Benchmark to a specific revision for a consistent release. (#641)

* Change adds functionality to GPT2 checkpoint writing.  Two of the layers were missing in the writing process.  Also added copy facility to the FileSystem protocol to copy the auxiliary files to the checkpoint location.

Co-authored-by: Brennan Saeta <[email protected]>
Co-authored-by: Brad Larson <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants