replicate/cog

End to end tests should clean up after themselves

Closed

#104 opened on May 31, 2021

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Python (356 forks)batch import
good first issuetype/chore

Repository metrics

Stars
 (5,724 stars)
PR merge metrics
 (Avg merge 7d 8h) (19 merged PRs in 30d)

Description

My machine is filled with this stuff.

Contributor guide

Research direction
Find where end to end tests create temporary files and ensure they are deleted after test completion.
Tech stack
python
Domain
testing
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75