Skip to content

Conversation

@wconstab
Copy link
Contributor

@wconstab wconstab commented Apr 5, 2022

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Apr 5, 2022

🔗 Helpful links

💊 CI failures summary and remediations

As of commit 79d341a (more details on the Dr. CI page):


  • 1/1 failures introduced in this PR

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages

See GitHub Actions build pull / linux-xenial-cuda11.3-py3.7-gcc7-bazel-test / build-and-test (1/1)

Step: "Build" (full log | diagnosis details | 🔁 rerun)

2022-04-05T17:56:02.2489774Z �[36;1m echo "ERR...t available for the merge-base of your branch"�[0m
2022-04-05T17:56:02.2486917Z �[36;1mfi�[0m
2022-04-05T17:56:02.2487149Z �[36;1m# Covers the case where a previous tag doesn't exist for the tree�[0m
2022-04-05T17:56:02.2487488Z �[36;1m# this is only really applicable on trees that don't have `.circleci/docker` at its merge base, i.e. nightly�[0m
2022-04-05T17:56:02.2487801Z �[36;1mif ! git rev-parse "$MERGE_BASE:.circleci/docker"; then�[0m
2022-04-05T17:56:02.2488142Z �[36;1m  echo "Directory '.circleci/docker' not found in commit $MERGE_BASE, you should probably rebase onto a more recent commit"�[0m
2022-04-05T17:56:02.2488426Z �[36;1m  exit 1�[0m
2022-04-05T17:56:02.2488588Z �[36;1mfi�[0m
2022-04-05T17:56:02.2488811Z �[36;1mPREVIOUS_DOCKER_TAG=$(git rev-parse "$MERGE_BASE:.circleci/docker")�[0m
2022-04-05T17:56:02.2489139Z �[36;1m# If no image exists but the hash is the same as the previous hash then we should error out here�[0m
2022-04-05T17:56:02.2489444Z �[36;1mif [[ "${PREVIOUS_DOCKER_TAG}" = "${DOCKER_TAG}" ]]; then�[0m
2022-04-05T17:56:02.2489774Z �[36;1m  echo "ERROR: Something has gone wrong and the previous image isn't available for the merge-base of your branch"�[0m
2022-04-05T17:56:02.2490171Z �[36;1m  echo "       contact the PyTorch team to restore the original images"�[0m
2022-04-05T17:56:02.2490410Z �[36;1m  exit 1�[0m
2022-04-05T17:56:02.2490572Z �[36;1mfi�[0m
2022-04-05T17:56:02.2490757Z �[36;1mecho ::set-output name=rebuild::yes�[0m
2022-04-05T17:56:02.2502185Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-04-05T17:56:02.2502420Z env:
2022-04-05T17:56:02.2502565Z   IN_CI: 1
2022-04-05T17:56:02.2502724Z   IS_GHA: 1
2022-04-05T17:56:02.2502907Z   GIT_DEFAULT_BRANCH: master
2022-04-05T17:56:02.2503131Z   BASE_REVISION: b64e7dee512c5696457500b3de7c60ecb0e93870

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

wconstab added a commit that referenced this pull request Apr 5, 2022
ghstack-source-id: 87fa17e
Pull Request resolved: #75264
@wconstab wconstab requested review from JackCaoG and bdhirsh April 5, 2022 17:54
Copy link
Collaborator

@JackCaoG JackCaoG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Copy link
Contributor

@bdhirsh bdhirsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@wconstab
Copy link
Contributor Author

wconstab commented Apr 5, 2022

@wconstab has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

facebook-github-bot pushed a commit that referenced this pull request Apr 6, 2022
Summary:
Pull Request resolved: #75264

Fixes one of the issues in pytorch/xla#3472

Test Plan: Imported from OSS

Reviewed By: bdhirsh

Differential Revision: D35411210

Pulled By: wconstab

fbshipit-source-id: 438535e0ea2f2eb5b138e2e64b008c2213a52f94
@github-actions
Copy link
Contributor

github-actions bot commented Apr 6, 2022

Hey @wconstab.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

@wconstab wconstab added topic: not user facing topic category release notes: lazy release notes category labels Apr 6, 2022
@facebook-github-bot facebook-github-bot deleted the gh/wconstab/1/head branch April 9, 2022 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants