Skip to content

Skip some CI jobs to save resources #65

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

Closed
wants to merge 2 commits into from

Conversation

eriknw
Copy link
Member

@eriknw eriknw commented May 4, 2023

This is a low-tech "hack" to save CI resources. I don't think we have a particularly strong dependency on Python version or OS, so it feels wasteful to test against the full matrix every time. Skipping some randomly still gives us an eventual guarantee that we'll catch an unlikely bug that e.g. only occurs on Windows on Python 3.9.

An alternative approach could be to randomly choose an OS, then run all Python versions with that OS for a single CI run (b/c I suspect we're more likely to break b/c of Python version instead of OS, but I don't really know).

@eriknw eriknw added the hygiene Improve code quality and reduce maintenance overhead label May 4, 2023
@eriknw
Copy link
Member Author

eriknw commented May 4, 2023

Would love it if GA supported graceful exit/cancellation of a job: actions/runner#662 and https://github.com/orgs/community/discussions/27174

@eriknw
Copy link
Member Author

eriknw commented May 4, 2023

Closing. I don't think this scales well. I would rather run a fixed number of jobs--such as one per Python version--then randomize OS and also randomize version of python-graphblas.

@eriknw eriknw closed this May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hygiene Improve code quality and reduce maintenance overhead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant