databricks/spark-deep-learning

Unitest is too Slow

Open

#65 opened on Oct 19, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (503 forks)batch import
devtoolhelp wanted

Repository metrics

Stars
 (1,979 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Run all Unitest take almost 30m. I guess we may optimize the time.

Contributor guide

Research direction
Profile the unit tests to identify slow tests, then consider parallelizing test execution, reducing test data size, or mocking external dependencies.
Tech stack
python
Domain
testing
Issue type
Performance
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
PythonApache SparkUnit testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65