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

Add a CI run that only tests non-optional deps (optimistically) #3646

Closed

Conversation

ml-evs
Copy link
Contributor

@ml-evs ml-evs commented Feb 22, 2024

Hopefully all tests have been written in such a way that they will be skipped if the underlying required package is not found... this would hopefully catch issues like #3645 ahead of time (although better linting would do the same too and avoid the potential need to update tests to skip if packages are missing -- only the implementation code would need to include package guard).

This should be updated after #3645 is merged to see what's left: not sure if adding a whole additional test run is "worth it" for the maintainers here but it definitely shows up the issues presented and would also be robust to any weirdness with optional deps changing the values of expected tests. There might be some kind of pytest plugin that lets you re-run only the skipped tests in the previous step when considering all deps.

@ml-evs ml-evs force-pushed the ml-evs/ci-with-mandatory-deps branch 3 times, most recently from 4372c4c to c9e9b24 Compare February 22, 2024 15:32
@janosh
Copy link
Member

janosh commented Feb 22, 2024

wow, that's way more possibly unbound variables than expected... 😅

- Hopefully all tests have been written in such a way that they will be
  skipped if the underlying required package is not found
@ml-evs ml-evs force-pushed the ml-evs/ci-with-mandatory-deps branch from c9e9b24 to 93e9afe Compare February 23, 2024 10:36
Signed-off-by: Matthew Evans <7916000+ml-evs@users.noreply.github.com>
@ml-evs
Copy link
Contributor Author

ml-evs commented Mar 29, 2024

@coderabbitai ignore

@materialsproject materialsproject deleted a comment from coderabbitai bot Mar 29, 2024
@janosh
Copy link
Member

janosh commented Mar 29, 2024

my impression is coderabbitai is too verbose. if it has useful suggestions, they are buried in a lot of boilerplate language that you don't want to read

@DanielYang59
Copy link
Contributor

Here I come! Giving you a hand on all those pyright fixes. I wish you don't mind :)

@ml-evs
Copy link
Contributor Author

ml-evs commented Apr 13, 2024

Just to be clear I was never planning on making these fixes, I just wanted to show the issue by adding it to the CI. So feel free to close/take over/supersede this PR

@DanielYang59
Copy link
Contributor

DanielYang59 commented Apr 13, 2024

Thanks for the input. I could help fix them and I could either push my fixes to your branch or maybe open a separate PR :) ? Which do you prefer (I'm not very experienced and would like to hear about your suggestions)?

@ml-evs
Copy link
Contributor Author

ml-evs commented Apr 13, 2024

Probably best to close this one and start again, the CI changes I suggested here are already out of date it seems. pyright was just being used to look for symptoms of the problem, the real change that needs to be made is running the test suite with mandatory deps only and making sure nothing fails.

@ml-evs ml-evs closed this Apr 13, 2024
@DanielYang59
Copy link
Contributor

Thanks for clarifying. I would redirect the PR directly to upstream if you don't mind (wasn't planning to pre-empt you)?

@ml-evs
Copy link
Contributor Author

ml-evs commented Apr 13, 2024

I won't be doing anything further on this so please go ahead!

@DanielYang59
Copy link
Contributor

Thanks!

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.

3 participants