Skip to content

Conversation

@ajtritt
Copy link
Contributor

@ajtritt ajtritt commented Dec 4, 2020

What does this PR do?

Add support for running PyTorch Lightning on systems managed by LSF.

Before submitting

  • Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
  • Did you make sure to update the documentation with your changes?
  • Did you write any new necessary tests?
  • Did you verify new and existing tests pass locally with your changes?
  • If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?

Always.

@SeanNaren SeanNaren added the distributed Generic distributed-related topic label Dec 4, 2020
@SeanNaren
Copy link
Contributor

Thanks!! Looks good, would you be able to confirm it works on your end here when you can?

@SeanNaren SeanNaren self-requested a review December 4, 2020 16:26
@edenlightning edenlightning added this to the 1.1.x milestone Dec 8, 2020
Copy link
Member

@justusschock justusschock left a comment

Choose a reason for hiding this comment

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

Is there a way to test this. I'm not fond to add anything to the Codename we cannot Test somehow in ci, since we are currently improving on that.

@ajtritt
Copy link
Contributor Author

ajtritt commented Dec 11, 2020

Is there a way to test this. I'm not fond to add anything to the Codename we cannot Test somehow in ci, since we are currently improving on that.

I think you would need access to a system that's managed by LSF. How does SLURM support get tested?

@pep8speaks
Copy link

pep8speaks commented Dec 11, 2020

Hello @ajtritt! Thanks for updating this PR.

Line 39:1: E302 expected 2 blank lines, found 0

Line 20:1: E302 expected 2 blank lines, found 1

Line 176:1: W391 blank line at end of file

Comment last updated at 2020-12-12 00:51:01 UTC

@ajtritt ajtritt closed this Dec 11, 2020
@ajtritt ajtritt reopened this Dec 11, 2020
@ajtritt ajtritt closed this Dec 11, 2020
@ajtritt ajtritt reopened this Dec 12, 2020
@ajtritt
Copy link
Contributor Author

ajtritt commented Dec 12, 2020

Will open a new PR

@ajtritt ajtritt closed this Dec 12, 2020
@ajtritt ajtritt mentioned this pull request Dec 12, 2020
11 tasks
@Borda
Copy link
Collaborator

Borda commented Dec 12, 2020

Will open a new PR

Any reason why this was closed? =)

@ajtritt
Copy link
Contributor Author

ajtritt commented Dec 12, 2020

Will open a new PR

Any reason why this was closed? =)

The final set of changes are more than the original PR stated. I could have edited the PR description, but that's a silent action and I didn't want the changes to be missed by reviewers.

@Borda
Copy link
Collaborator

Borda commented Dec 13, 2020

I think it would be completely fine to edit the description, reset all reviews, and comment that you extend the scope :]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

distributed Generic distributed-related topic

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants