CI coverage for batch launchers
- Linguagem predominante
- Jupyter Notebook
- Estrelas
- 2.6k
- Forks
- 1k
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
We have CI coverage for batch through SLURM, but not the other batch launchers (beyond template generation).
[dask-jobqueue][] has CI for most of our supported batch systems, deployed via docker-compose. We could adapt their setup to get proper exercise of all of most of our supported cluster types.
[dask-jobqueue]: https://github.com/dask/dask-jobqueue/tree/0.7.3/ci
It should mostly be a find-replace of installing dask to installing ipyparallel, since all the cluster setup itself should be reusable.
Guia de contribuição
Direção de pesquisa
Start with the dask-jobqueue ci directory linked in the issue and compare its docker-compose batch-system setup with ipyparallel's existing SLURM CI coverage. Adapt the setup to install ipyparallel and exercise the other supported batch launchers, with CI runs demonstrating coverage beyond template generation.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- docker-compose, python
- Domínio
- ci-cd, distributed-systems
- Tipo de issue
- Funcionalidade
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 35/100