pytorch
8e63199c - .github: Always run chown workspace (#64854)

Commit

3 years ago

.github: Always run chown workspace (#64854) Summary: In some workflow runs, like https://github.com/pytorch/pytorch/runs/3568714658, the chown workspace step is duplicated. Is that intentional? Unfortunately it is pretty necessary since (w/ docker) the folder can sometimes be in a broken permission state before and after we run jobs. So this PR makes the second chown workspace run always because that's the true intention of the step. Pull Request resolved: https://github.com/pytorch/pytorch/pull/64854 Reviewed By: jbschlosser, seemethere Differential Revision: D30879289 Pulled By: janeyx99 fbshipit-source-id: 4157ff826c86e8c912deb1ba0cb5c47ea7596529

References

#65112 - [LTC] Merge master

Author

janeyx99

Committer

facebook-github-bot

Parents

70e64fed

Files15

.github
- templates
  - common.yml.j2
- workflows
  - generated-libtorch-linux-xenial-cuda10.2-py3.6-gcc7.yml
  - generated-libtorch-linux-xenial-cuda11.3-py3.6-gcc7.yml
  - generated-linux-bionic-cuda10.2-py3.9-gcc7.yml
  - generated-linux-bionic-py3.6-clang9.yml
  - generated-linux-bionic-py3.8-gcc9-coverage.yml
  - generated-linux-xenial-cuda10.2-py3.6-gcc7.yml
  - generated-linux-xenial-cuda11.3-py3.6-gcc7.yml
  - generated-linux-xenial-py3.6-gcc5.4.yml
  - generated-linux-xenial-py3.6-gcc7-bazel-test.yml
  - generated-parallelnative-linux-xenial-py3.6-gcc5.4.yml
  - generated-paralleltbb-linux-xenial-py3.6-gcc5.4.yml
  - generated-periodic-libtorch-linux-xenial-cuda11.1-py3.6-gcc7.yml
  - generated-periodic-linux-xenial-cuda11.1-py3.6-gcc7.yml
  - generated-puretorch-linux-xenial-py3.6-gcc5.4.yml

pytorch 8e63199c - .github: Always run chown workspace (#64854)

pytorch
8e63199c - .github: Always run chown workspace (#64854)