iterative / iterative/PyDrive2
tests: concurrency
Offen
enhancement
- Vorherrschende Sprache
- Python
- Sterne
- 670
- Forks
- 75
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
The tests are not designed to run concurrently.
- one job from a PR build can failed at the same time as a job from a branch build because they interfere with each other
- tests are slow as they are not run in parallel
Really should fix this (e.g. timestamp filenames)
- from https://github.com/iterative/PyDrive2/pull/33#issuecomment-624853154
Beitragsleitfaden
Rechercherichtung
Start by tracing how the tests in pull-request and branch builds create and share filenames or other resources. Make concurrent jobs independent, including through unique timestamp-based filenames where appropriate, and verify that tests can run in parallel without interference.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- python
- Bereich
- ci-cd, testing
- Issue-Typ
- Refactoring
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100