Skip to content
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

Delete tox.ini #1799

Merged
merged 1 commit into from
Jul 26, 2022
Merged

Delete tox.ini #1799

merged 1 commit into from
Jul 26, 2022

Conversation

miguelgfierro
Copy link
Collaborator

@miguelgfierro miguelgfierro commented Jul 20, 2022

Description

I think we are not using tox anymore. Earlier today I tried to run the tests with pytest, and I got an error because I have this file. Should we erase it?

FYI @laserprec

Related Issues

Checklist:

  • I have followed the contribution guidelines and code style for this project.
  • I have added tests covering my contributions.
  • I have updated the documentation accordingly.
  • This PR is being made to staging branch and not to main branch.



# Configurations for running pytest
[pytest]
Copy link
Contributor

@laserprec laserprec Jul 20, 2022

Choose a reason for hiding this comment

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

I am okay with deleting but tox also stores configuration related to other python tools like pytest and flake8. Maybe the error is relating them. Do you think we would need any of these configurations?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I would ask back a question, is there anything in the tox that we can reused in the workflow that @pradnyeshjoshi did https://github.com/microsoft/recommenders/tree/main/.github/workflows

# reports all (except passed tests). See https://docs.pytest.org/en/latest/usage.html#detailed-summary-report
-ra
--durations 10
--cov-append --cov=recommenders --cov-report=term --cov-report=xml --junitxml=junit/test-results.xml
Copy link
Contributor

Choose a reason for hiding this comment

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

I think by default we report code coverage at the end of the tests. Maybe the error you are seeing is relating to missing the coverage package?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@pradnyeshjoshi in the AzureML tests, do we have coverage report?

@miguelgfierro miguelgfierro merged commit 3ccc487 into staging Jul 26, 2022
@miguelgfierro miguelgfierro deleted the miguelgfierro-patch-1 branch July 26, 2022 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants