-
Notifications
You must be signed in to change notification settings - Fork 323
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
ci: Fix dataset downloading errors #387
ci: Fix dataset downloading errors #387
Conversation
Codecov Report
@@ Coverage Diff @@
## master #387 +/- ##
==========================================
- Coverage 81.18% 80.88% -0.31%
==========================================
Files 100 100
Lines 5714 5701 -13
==========================================
- Hits 4639 4611 -28
- Misses 1075 1090 +15
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
This is a false statement... Some tests are still failing other than doctest. |
I agree with @akihironitta the point why doctests may seem to be failing more is they are executed before other tests in the tests folder :] |
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.
can we just temporary in one run print what is content of the Dataset folder so see if it restored correctly and eventually fro each DataModule show the source folder...
ba06265
to
257a0db
Compare
In docstrings of datasets/datamodules, we're not using For example, the following test command tries to download and save
Fixed in faeebf2. |
1f8ad76
to
257a0db
Compare
Not sure why the tests on windows tend to fail very often... |
Might be off topic, but I just realised that
WIP in #409. |
Seems the last number of ci runs on windows went good without any problems... Not sure why WIP in #409. |
@akihironitta how is it going, can I help somehow? 🐰 |
@Borda I was trying to reproduce the error, Now, I'll be making several empty commits again to run the tests in parallel to reproduce the error and to see if the cifar10 is correctly cached. |
Now, all say
This is only a side note, but it is strange that on runs on the same commit 30a7f6d, the hash value on windows is different from the ones on macOS and Ubuntu. |
|
looks strange, they say that GH actions are still in development but as much... :] |
@Borda Right... so what else do you think we can do here? I don't think I can solve this problem because I cannot reproduce the error Also, shall we try to fix the below error which happens very often in #409? (All the runs on the two commits right above this comment failed due to this.)
|
feb8f77
to
3d49fd4
Compare
Closing this PR as there isn't anything to investigate on this further. |
What does this PR do?
As pointed out in #377 (comment) by @Borda, the tests try to download datasets, which sometimes fail with the following error:
Description of the changes
It seems that those failing tests are often doctest, so this PR simply removes the doctest fromci_test-full.yml
as we still have doctest inci_test-base.yml
.https://github.com/PyTorchLightning/pytorch-lightning-bolts/blob/b8ac85154465956b06fd1005b21b071af5493f11/.github/workflows/ci_test-full.yml#L86https://github.com/PyTorchLightning/pytorch-lightning-bolts/blob/b8ac85154465956b06fd1005b21b071af5493f11/.github/workflows/ci_test-base.yml#L69This PR also includes minor changes in some tests usingSee tests: Use cached datasets in LitMNIST and the doctests #414.LitMNIST
to utilize dataset caching since they currently download and store MNIST datasets in./
instead of in./datasets/
(datadir
fixture).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 🙃