-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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 StragglerDetection and FTlauncher to NeMo2.0 #11117
Conversation
[🤖]: Hi @ShriyaPalsamudram 👋, We wanted to let you know that a CICD pipeline for this PR just finished successfully So it might be time to merge this PR or get some approvals I'm just a bot so I'll leave it you what to do next. //cc @pablo-garay @ko3n1g |
6382449
to
a14a642
Compare
@maanug-nv to introduce abstraction to reduce number of files changed to add a callback for all recipes. |
598d275
to
eeb9414
Compare
[🤖]: Hi @ShriyaPalsamudram 👋, We wanted to let you know that a CICD pipeline for this PR just finished successfully So it might be time to merge this PR or get some approvals I'm just a bot so I'll leave it you what to do next. //cc @pablo-garay @ko3n1g |
38fce0d
to
a92e667
Compare
nemo/lightning/run/plugins.py
Outdated
assert any( | ||
map( | ||
lambda callback: ( | ||
callback.__fn_or_cls__ == PreemptionCallback if '__fn_or_cls__' in dir(callback) else False |
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.
Why does Nsys not work with Preemption? is this supposed to be FaultToleranceCallback ?
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 assert is part of the ConfigValidationPlugin
where we are validating Preemption callback. Only change here is to add if '__fn_or_cls__' in dir(callback) else False
because there was some other callback that didn't have __fn_or_cls__
and hence this assert was failing.
Signed-off-by: ShriyaPalsamudram <[email protected]>
Signed-off-by: Shriya Palsamudram <[email protected]>
Signed-off-by: Shriya Palsamudram <[email protected]>
Signed-off-by: Shriya Palsamudram <[email protected]>
Signed-off-by: Shriya Palsamudram <[email protected]>
Signed-off-by: Shriya Palsamudram <[email protected]>
Signed-off-by: ShriyaPalsamudram <[email protected]>
Signed-off-by: Shriya Palsamudram <[email protected]>
Signed-off-by: Shriya Palsamudram <[email protected]>
Signed-off-by: ShriyaPalsamudram <[email protected]>
Signed-off-by: Shriya Palsamudram <[email protected]>
442bd12
to
7f27da9
Compare
Signed-off-by: Shriya Palsamudram <[email protected]>
Signed-off-by: Shriya Rishab <[email protected]>
assert "Straggler report processing time" in log_content | ||
if args.crash_step: | ||
assert f"Exception: Simulating a crash at step {args.crash_step}!" in log_content | ||
|
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.
We should somehow confirm that we still finish the training despite the crash, right? Maybe the common.verify_ckpt_dir will be enough, it should ensure that there's a checkpoint for step 20.
1f08f43
to
fd55915
Compare
beep boop 🤖: 🚨 The following files must be fixed before merge! Your code was analyzed with PyLint. The following annotations have been identified:
Thank you for improving NeMo's documentation! |
beep boop 🤖: 🙏 The following files have warnings. In case you are familiar with these, please try helping us to improve the code base. Your code was analyzed with PyLint. The following annotations have been identified:
Thank you for improving NeMo's documentation! |
Close PR as the tests are being added as part of #11406 |
What does this PR do ?
Add StragglerDetection and FTlauncher to NeMo2.0
Collection: [Note which collection this PR will affect]
Changelog
Usage
# Add a code snippet demonstrating how to use this
GitHub Actions CI
The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.
The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".
Before your PR is "Ready for review"
Pre checks:
PR Type:
If you haven't finished some of the above items you can still open "Draft" PR.
Who can review?
Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.
Additional Information