ipython / ipython/ipyparallel

CI coverage for batch launchers

Offen
#604 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Jupyter Notebook
Sterne
2.6k
Forks
1k
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
docker-compose, python
Bereich
ci-cd, distributed-systems
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.