-
Notifications
You must be signed in to change notification settings - Fork 30.9k
Add Doc Test GPT-J #16507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Doc Test GPT-J #16507
Conversation
|
The documentation is not available anymore as the PR was closed or merged. |
|
Thank you for working on GPT-J. |
yep please do and let me know and we can close this =) |
|
Hi, @ArEnSc After discussing with the team, we found that there is no real checkpoints for finetuned GPT-J model on downstream tasks. (There is one for text seq. classification, but it is for Korean language). If you still want to work on this GPT-J doctest, the best we could do for now is to use a tiny model (that is created for testing purpose) https://huggingface.co/hf-internal-testing/tiny-random-gptj With this one, there won't be any OOM issue. Let me know if you want to continue, and if so, don't hesitate if you have any issue using this tiny model checkpoint. Thanks! |
will do! Ill do this after work today |
|
Hi, @ArEnSc Thank you for the effort. I need to investigate first why it is non deterministic, and see if there is a way to fix this. I will take a look in this soon! |
|
Hi, @ArEnSc I uploaded the checkpoints I tested with |
Ran Style and Fixup.
|
@ydshieh I think we should be good to go here let me know =) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Run locally - tests pass.
LGTM. Let's wait @patil-suraj final review :-) before merging.
| if self.args.inference: | ||
| if self.args.memory: | ||
| memory, inference_summary = self.inference_memory(model_name, batch_size, sequence_length) | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need for this new line :-) Let's not change this file 🙏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be addressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
strange I will fix that soon
|
@ArEnSc Would you mind to remove the comments with (very) long error message - just easier to load this page :-) Thanks! |
|
@ydshieh looks like it good to go! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for working on this! Good for merge once the comment for benchmark_utils.py file is addressed :)
| if self.args.inference: | ||
| if self.args.memory: | ||
| memory, inference_summary = self.inference_memory(model_name, batch_size, sequence_length) | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be addressed.
Then refactored tests to const variables.
…to add-doc-test-gptj
|
@ydshieh I think this is done after CI passes =) |
|
@ydshieh we are good to merge! =) |
* Required the values GPTJ unfortunately cannot run the model =) * Added the file to the doc tests * Run Fixup and Style * Fixed with the test versions of gptj. Ran Style and Fixup. * Trigger ci * A Minor Change to License * Fixed spacing added to the benchmark_utils. Then refactored tests to const variables. * Removed strings that were included as default parameters anyways. Co-authored-by: ArEnSc <xx.mike.chung.xx@gmail.com>
What does this PR do?
Fixes the broken doc tests for GPT-J
Apart of the documentation sprint work.
Before submitting
This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
Did you read the contributor guideline,
Pull Request section?
Was this discussed/approved via a Github [issue] ([Community Event] Doc Tests Sprint #16292)? Please add a link
to it if that's the case.
Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
Did you write any new necessary tests?
Who can review?
@ydshieh
@sgugger
-->