-
Notifications
You must be signed in to change notification settings - Fork 212
simplify examples #57
Conversation
Codecov Report
@@ Coverage Diff @@
## master #57 +/- ##
==========================================
+ Coverage 80.31% 80.37% +0.05%
==========================================
Files 47 47
Lines 1387 1391 +4
==========================================
+ Hits 1114 1118 +4
Misses 273 273
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
I believe the examples hang with |
not really, they are not even called anywhere :D |
We do test some of them: https://github.com/PyTorchLightning/lightning-flash/blob/master/tests/examples/test_examples.py Also So the tests are not checking if it hangs |
yes but here you test just some of them and the execution is called from tests folder |
if/main is needed in order for the dataloaders to function properly (because of multiprocessing) |
so the script is called in a subprocess, but it does not have if/main it is empty so when/how it is called? |
As I said, try uncommenting And let's see if CI passes |
Hello @Borda! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-02-03 08:11:10 UTC |
trying now, but as it is, you preventing the hanging n two fronts - in examples and restricting workers to 0 |
@carmocca seems to be fine, no hanging... |
The failing MacOS tests seem to show otherwise 😆 |
let's see if the updated nb workers pass on the master - https://github.com/PyTorchLightning/lightning-flash/actions/runs/532388784 |
I'm not sure about what are you trying to say. But you just removed both fronts. And in any case, we cant fix num_workers 0 forever. So that's why the examples require |
Because you asked for it, so I am returning to workers count 0 |
What does this PR do?
since we do not run tests on examples anyway there is o reason to have them wrap in main especially since there is nothing else than main anyway...
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 🙃