-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
repair CI for Win #2358
repair CI for Win #2358
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2358 +/- ##
======================================
- Coverage 88% 88% -0%
======================================
Files 70 70
Lines 5555 5567 +12
======================================
+ Hits 4889 4893 +4
- Misses 666 674 +8 |
@awaelchli, failing for Windows:
|
Hello @Borda! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-06-26 22:50:53 UTC |
@Borda the distributed part is fixed. only the horovod part still persists |
@tgaddair we may have some problem with Horovod on Win, is it supported? |
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.
In the horovod test, don't we also have tp either skip it or change the backend and remove the horovod size asserts?
Hey @Borda, Horovod is not supported on Windows. Thanks for checking! |
@tgaddair this is very strange as it is in try/except
|
@awaelchli @justusschock @PyTorchLightning/core-contributors any idea why it fails even during the test collection before running any test? just for Windows... :/ |
fixed the failing but for some reason, the Win CI is super slow... |
The tests became slow for me since the ddp mode was switched from spawn. I'm pretty sure that's it. |
so shall we test by default |
sure that would work. but we need at least one ddp test. |
try num_workers=0 in tests. it will speed up on windows. but probably on linux and mac it will be slower then. |
it runs all tests for all ddp as before just replace the default one, so all functionality is tested |
Co-authored-by: Peter Yu <2057325+yukw777@users.noreply.github.com>
…on Windows (#2294) * Fix load_from_checkpoint() not working with URL on Windows * Update CHANGELOG * Update CHANGELOG.md Co-authored-by: Peter Yu <2057325+yukw777@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Jirka Borovec <Borda@users.noreply.github.com> Co-authored-by: Peter Yu <2057325+yukw777@users.noreply.github.com>
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 was a tough one :)
@awaelchli, sorry for the late response! I’ve been traveling for the past few days and just saw this. It seems like you guys figured it out though. What was the issue with Windows? |
@@ -48,7 +48,7 @@ def translate_path(self, path): | |||
class ThreadingHTTPServer(ThreadingMixIn, HTTPServer): | |||
daemon_threads = True | |||
|
|||
with ThreadingHTTPServer(('', 0), Handler) as server: | |||
with ThreadingHTTPServer(('localhost', 0), Handler) as server: |
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.
Ah man!!
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.
hey no problem.
yep that was it, Windows didn't like the 0.0.0.0 address :)
There were a couple of them as all Win tests were ignored for a few weeks or months... |
What does this PR do?
it seems like Win CI was falling but the checks were passed
https://github.com/PyTorchLightning/pytorch-lightning/pull/2356/checks?check_run_id=805809911
The issue was reported in nedbat/coveragepy#1003
Fixes #2347
Fixes #2357
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃