Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Comments

Close side panel

add success messages for generate train convert evaluate test cmds#2741

Merged
mergify[bot] merged 1 commit intoinstructlab:maininstructlab/instructlab:mainfrom
reidliu41:add-success-msg-for-cmdsreidliu41/instructlab:add-success-msg-for-cmdsCopy head branch name to clipboard
Jan 6, 2025
Merged

add success messages for generate train convert evaluate test cmds#2741
mergify[bot] merged 1 commit intoinstructlab:maininstructlab/instructlab:mainfrom
reidliu41:add-success-msg-for-cmdsreidliu41/instructlab:add-success-msg-for-cmdsCopy head branch name to clipboard

Conversation

@reidliu41
Copy link
Contributor

@reidliu41 reidliu41 commented Dec 4, 2024

for 2740

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the
    conventional commits.
  • Changelog updated with breaking and/or notable changes for the next minor release.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Functional tests have been added, if necessary.
  • E2E Workflow tests have been added, if necessary.

@mergify mergify bot added testing Relates to testing ci-failure PR has at least one CI failure and removed ci-failure PR has at least one CI failure labels Dec 4, 2024
@reidliu41 reidliu41 force-pushed the add-success-msg-for-cmds branch from b62f34f to d3f03d2 Compare December 4, 2024 05:02
@ktam3 ktam3 linked an issue Dec 4, 2024 that may be closed by this pull request
Copy link
Member

@nathan-weinberg nathan-weinberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Honestly, I like the emojis - it's a go from Nathan

@mergify mergify bot added the one-approval PR has one approval from a maintainer label Dec 10, 2024
turn2_score = round(turn2_score, 2)
print(turn2_score)
display_error_rate(error_rate)
click.echo("\n✅ Model evaluate with MTBENCH completed successfully!")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MTBENCH here and MtBenchBranch below are inconsistent.

I am not really sure this is helpful for the eval cases. Given the results are displayed at the end, it seems pretty obvious already.

nit: Note that it's also possible you have a very high error rate and it's not really a "success"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, what do you mean of inconsistent ?
Yeah, may remove successfully , just mention finish.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was referring to the case differences between MTBENCH and MtBenchBranch

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it ok for MTBench and MTBenchBranch (check it from README.md)?

eval_gpus=ctx.obj.config.evaluate.gpus,
training_journal=training_journal,
)
click.echo("✅ Model train with accelerated completed successfully!")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are all tricky since other messages are being printed throughout the code. For example with case I think you might already get a:

Training finished! Best final checkpoint: /tmp/tmp.01L0NjBZlG/.local/share/instructlab/skills-only/phase2/checkpoints/hf_format/samples_616 with score: 8.368421052631579

Also nit: This message might be better worded as:

Accelerated model training completed successfully!

(Similar for the other train messages below)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, just checked, seems finished only for accelerated train, there is no msg for simple and full

system_prompt,
legacy_pretraining_format,
)
click.echo("✅ Data generate completed successfully!")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any concerns about character compatibility with the ✅ across terminals or other supported environments?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re-considering whether can add a simple check first.

@cdoern
Copy link
Contributor

cdoern commented Dec 12, 2024

I really like the ✅ but I also worry about how this will render especially in log files.

could we do some ascii drawing or something like we have when training starts?

print("ᕙ(•̀‸•́‶)ᕗ Training has started! ᕙ(•̀‸•́‶)ᕗ ")

ᕙ(•̀‸•́‶)ᕗ

@reidliu41
Copy link
Contributor Author

I really like the ✅ but I also worry about how this will render especially in log files.

could we do some ascii drawing or something like we have when training starts?

print("ᕙ(•̀‸•́‶)ᕗ Training has started! ᕙ(•̀‸•́‶)ᕗ ")

ᕙ(•̀‸•́‶)ᕗ

i think is good to have a try

@reidliu41 reidliu41 force-pushed the add-success-msg-for-cmds branch from d3f03d2 to d782769 Compare December 13, 2024 03:54
@mergify mergify bot added ci-failure PR has at least one CI failure and removed ci-failure PR has at least one CI failure labels Dec 13, 2024
@reidliu41 reidliu41 force-pushed the add-success-msg-for-cmds branch from 0810710 to 9566507 Compare December 13, 2024 04:07
@reidliu41
Copy link
Contributor Author

hi @danmcp @cdoern updated
I select this one ᕦ(òᴗóˇ)ᕤ
A fun and energetic expression of confidence and accomplishment after completing a task.

@reidliu41 reidliu41 requested a review from danmcp December 16, 2024 21:16
@mergify mergify bot removed the one-approval PR has one approval from a maintainer label Dec 20, 2024
@mergify mergify bot merged commit b483e27 into instructlab:main Jan 6, 2025
@bbrowning
Copy link
Contributor

FYI this didn't fail in the pre-merge testing, but will break all the large/xlarge CI jobs until we change

grep "Training finished! Best final checkpoint: " "${E2E_TEST_DIR}"/skills_only_training.log | grep -o "/[^ ]*"
- that needs to look for the new log message that was changed in this PR.

@reidliu41 reidliu41 mentioned this pull request Jan 7, 2025
6 tasks
mergify bot added a commit that referenced this pull request Jan 7, 2025
For #2741 (comment)

**Checklist:**

- [ ] **Commit Message Formatting**: Commit titles and messages follow guidelines in the
  [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/#summary).
- [ ] [Changelog](https://github.com/instructlab/instructlab/blob/main/CHANGELOG.md) updated with breaking and/or notable changes for the next minor release.
- [ ] Documentation has been updated, if necessary.
- [ ] Unit tests have been added, if necessary.
- [ ] Functional tests have been added, if necessary.
- [ ] E2E Workflow tests have been added, if necessary.



Approved-by: cdoern

Approved-by: bbrowning

Approved-by: nathan-weinberg
@reidliu41 reidliu41 mentioned this pull request Jan 8, 2025
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testing Relates to testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

add a success message for different commands Add Confirmation and Next Steps for Model Download Command (ilab model download)

6 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.