pytorch

7a792879 - Prevent clobbering of docker images by parallelnative/paralleltbb builds (#39863)

Prevent clobbering of docker images by parallelnative/paralleltbb builds (#39863) Summary: Pull Request resolved: https://github.com/pytorch/pytorch/pull/39863 The paralleltbb and parallelnative builds use the same docker image as pytorch-linux-trusty-py3.6-gcc5.4-build (https://github.com/pytorch/pytorch/blob/da3073e9b1db503f106842339f50f522d973be84/.circleci/config.yml#L6752) Therefore they should push to a different intermediate docker image for the next phase (testing), according to (https://github.com/pytorch/pytorch/blob/da3073e9b1db503f106842339f50f522d973be84/.circleci/config.yml#L434-L439). However, they're not actually included in that list. We've found evidence of what looks like clobbering in recent CI jobs (https://circleci.com/gh/pytorch/pytorch/5787534?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link), (https://circleci.com/gh/pytorch/pytorch/5787763?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) This PR adds parallelnative and paralleltbb to the list to prevent clobbering. Test Plan: - Wait for CI tests to pass on this PR. - The paralleltbb and parallelnative builds don't actually run on PRs. So I think the plan here is to yolo land and hope it works. Differential Revision: D22002279 Pulled By: zou3519 fbshipit-source-id: 89f05cedb2fbde2dc3033458b1e0c5be0b194955