Skip to content

Conversation

@ocefpaf
Copy link
Member

@ocefpaf ocefpaf commented Dec 7, 2022

Closes #291 and incorporates #276.

@ocefpaf ocefpaf marked this pull request as ready for review December 8, 2022 00:05
@ocefpaf ocefpaf requested a review from abkfenris December 8, 2022 00:05
Copy link
Contributor

@abkfenris abkfenris left a comment

Choose a reason for hiding this comment

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

I think it looks ok, but it may be easier to tell when we do have failures if the steps in the core test are broken apart.

It may also be worth combining the core tests in as a new job in the current tests.yml, as it can be a bit quicker to navigate between different jobs in the same workflow than between jobs in different workflows.

Co-authored-by: Alex Kerney <abk@mac.com>
@ocefpaf
Copy link
Member Author

ocefpaf commented Dec 8, 2022

It may also be worth combining the core tests in as a new job in the current tests.yml, as it can be a bit quicker to navigate between different jobs in the same workflow than between jobs in different workflows.

I don't have a strong opinion on this but I'm slightly more inclined to multiple files than a huge one. Sure, it won't be a huge one right away but they can grow in size. In this cases the context is not only a small subset without the optional deps but also a non-conda setup.

@ocefpaf
Copy link
Member Author

ocefpaf commented Dec 8, 2022

I'll work on the docs in another PR. Let's get this one in.

@ocefpaf ocefpaf merged commit f11ad16 into ioos:main Dec 8, 2022
@ocefpaf ocefpaf deleted the fix_optional_deps branch December 8, 2022 14:32
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.

Refactor tests and mandatory vs optional dependencies

2 participants