tensorflow / tensorflow/model-optimization
OOM errors when running tests with bazel
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 349
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
Describe the bug
I had a lot of Out of Memory errors when running pruning tests with bazel.
This is what I tried on two different hardware (see below for configuration):
bazel test tensorflow_model_optimization/python/core/sparsity/keras/...
It gave me either a GPU->CPU Memcpy failed Fatal Python error: Aborted or a CUDA OOM on both hardware.bazel test tensorflow_model_optimization/python/core/sparsity/keras:prune_integration_test --runs_per_test=10
Only one file to test for, but 10 runs. Same result.bazel test tensorflow_model_optimization/python/core/sparsity/keras:prune_integration_test
Only one file to test for. It worked fine on hardware2, but did OOM on hardware1.bazel test tensorflow_model_optimization/python/core/sparsity/keras:prune_integration_test --runs_per_test=10 --jobs=1
No parallel runs. It worked fine on hardware2, but did OOM on hardware1.
System information
Hardware configuration1: >32gb ram, >10cpus, Quadro P400 (2gb).
Hardware configuration2: >64gb ram, >30cpus, x4 GeForce GTX TITAN X.
TensorFlow version (installed from source or binary): tf2.4 and tf-nightly (tried both)
TensorFlow Model Optimization version (installed from source or binary): source.
Python version: 3.8
Software configuration: Ubuntu, Cuda11, Bazel3.7.2.
Describe the expected behavior
Tests should work.
Describe the current behavior
Tests are flaky due to memory issues.
Code to reproduce the issue
bazel test tensorflow_model_optimization/python/core/sparsity/keras/...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test implementation is named. Start by reproducing the issue with bazel test tensorflow_model_optimization/python/core/sparsity/keras:prune_integration_test, then compare the broader pruning test target and runs with --jobs=1 on the reported hardware configurations. Done means the pruning tests complete without GPU or CPU out-of-memory failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, tensorflow
- Domain
- build-system, machine-learning, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100