-
Notifications
You must be signed in to change notification settings - Fork 3.6k
separate requirements for logger dependencies #792
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
separate requirements for logger dependencies #792
Conversation
…or the supported loggers
thanks! why do we need a separate requirements? we already have a different one in tests. |
ah thanks didn't know about that. The problem is, that we need to specify versions of optional packages (e.g. loggers) somewhere. More as a reference for users than a file for installing requirements. |
@williamFalcon as a user you do not want to install all testing packages, just those you need to run e.g. special logger... we have a warning message if you ale loading logger for which you do not have a package installed, but it is missing min version... |
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.
pls copy versions from tests/requirements.txt with minimal versions
then in tests/requirements.txt imports these extras like -r ../requirements-extra.txt
@Borda only test_tube had a minimal version. Copied that, added |
@Aljo-Rovco it would be great contributions to find out what is the min versions to pass all tests (you can try something like divide an conquer strategy =) |
will deal with this either today or tomorrow |
@Borda I assume you meant |
…extra.txt; increased the amount of training data that is used for tests
I increased the amount of data that is used when running the tests (from |
@Borda could you have a look at the failing checks? Not quite sure how to fix them |
@Aljo-Rovco you need to include or |
it seems there is an ussie with
|
had a look, but not sure how to solve it. |
it was working before so let's try to increase the wandb version... |
I think it was working before because the test didn't test much. It just created a logger:
All other tests actually trained a model |
also, isn't the last version used in the CI testing? |
add line in .github/workflow/ci-testing.yml
just belo the changing |
I would say you can try to fix it here or remove the new test and open issue where you describe the problem along with your proposed test... I would suggest to to to the second option so we keep the PR simple... sure you can take the new issue and solve it :] @Aljo-Rovco |
…irements-extra.txt in ci-testing.yml
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.
LGTM 🚀
@Aljo-Rovco pls create an issue with suggesting the tests you had here for |
Sorry, was busy. Will do |
created a new issue: #906 |
* added file that contains information on the minimal versions needed for the supported loggers * copied minimal version, combined files, deleted duplicates * sorted functions in tests/test_loggers.py to be consistent * expanded wandb logging test; added minimal versions for requirements-extra.txt; increased the amount of training data that is used for tests * formatting * added requirements-extra.txt to MANIFEST.in * reverted wandb test; ensured minimal version for dependencies in requirements-extra.txt in ci-testing.yml
Fixes #764.
The versions are the current versions of the respective packages.
I used all loggers in offline mode and they all seemed to work. Not sure how exhaustive the test should be.