SigKill when installing wheels for torch 1.7.1


Our team has torch==1.7.1 as a dependency in requirements.txt. When running bazel build on a target, I’m getting a SigKill action happening when wheels is being built for torch. It looks like at some point, bazel runs:

python3 -m pip --isolated wheel torch==1.7.1 which results in:

Collecting torch==1.7.1

If I run it as a part of my full bazel build, I get:

Collecting torch==1.7.1
 (Traceback (most recent call last):
  File "/usr/lib/python3.8/", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/", line 87, in _run_code
    exec(code, run_globals)
  File "/home/vagrant/.cache/bazel/_bazel_vagrant/f9910d98673307a31f928c448bd4acd0/external/rules_python/python/pip_install/extract_wheels/", line 5, in <module>
  File "/home/vagrant/.cache/bazel/_bazel_vagrant/f9910d98673307a31f928c448bd4acd0/external/rules_python/python/pip_install/extract_wheels/", line 87, in main, check=True)
  File "/usr/lib/python3.8/", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/home/vagrant/venv/bin/python3', '-m', 'pip', '--isolated', 'wheel', '-r', '/home/vagrant/tech-backends/requirements.txt']' died with <Signals.SIGKILL: 9>.

Does anyone know how to address this? I have python 3.8.5.