Skip to content

guard against issues where we try to access tensor_meta on non-tensor input#82611

Closed
Chillee wants to merge 1 commit intogh/chillee/88/basefrom
gh/chillee/88/head
Closed

guard against issues where we try to access tensor_meta on non-tensor input#82611
Chillee wants to merge 1 commit intogh/chillee/88/basefrom
gh/chillee/88/head

Conversation

@Chillee
Copy link
Collaborator

@Chillee Chillee commented Aug 1, 2022 •
edited
Loading

Chillee added a commit that referenced this pull request Aug 1, 2022
@Chillee
guard against issues where we try to access tensor_meta on non-tensor…
7e9a945 
… input

ghstack-source-id: f1f28fe
Pull Request resolved: #82611
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Aug 1, 2022 •
edited
Loading

🔗 Helpful links

❌ 1 New Failures

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

Expand to see more
  • 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-docs / build-docs (cpp) (1/1)

Step: "Build cpp docs" (full log | diagnosis details)

2022-08-01T23:26:02.8045389Z ##[error]Process completed with exit code 137. 
2022-08-01T23:22:16.3923981Z �[01mwriting output... �[39;49;00m[ 90%] �[32mapi/structat_1_1native_1_1_descriptor_deleter .. api/structtorch_1_1enumtype_1_1k_conv_transpose3_d�[39;49;00m
2022-08-01T23:22:25.4510385Z �[01mwriting output... �[39;49;00m[ 92%] �[32mapi/structtorch_1_1enumtype_1_1k_fan_in .. api/structtorch_1_1nn_1_1_huber_loss_options�[39;49;00m
2022-08-01T23:22:43.0989191Z �[01mwriting output... �[39;49;00m[ 93%] �[32mapi/structtorch_1_1nn_1_1_instance_norm_options .. api/structtorch_1_1nn_1_1functional_1_1_normalize_func_options�[39;49;00m
2022-08-01T23:22:50.3927081Z �[01mwriting output... �[39;49;00m[ 95%] �[32mapi/structtorch_1_1nn_1_1functional_1_1_pad_func_options .. api/typedef_namespacetorch_1_1nn_1_1functional_1a872abe58e376dc403b3bea4259d4d2b5�[39;49;00m
2022-08-01T23:22:55.3358721Z �[01mwriting output... �[39;49;00m[ 96%] �[32mapi/typedef_namespacetorch_1_1nn_1_1functional_1a8c6ad6948f1e1c554bc731c5d7081408 .. api/typedef_namespacetorch_1_1python_1_1detail_1a9808c29bfe27f974414c895b4ff37f2f�[39;49;00m
2022-08-01T23:23:07.3767906Z �[01mwriting output... �[39;49;00m[ 98%] �[32mapi/typedef_namespacetorch_1a23e4c6c3b3c89d2a8051db46fc003159 .. api/variable_namespacetorch_1aeaf16f038962bbc7c4a0f57696fa3fb1�[39;49;00m
2022-08-01T23:23:09.2537755Z �[01mwriting output... �[39;49;00m[100%] �[32mapi/variable_namespacetorch_1aec4dc7ff45a796efc14a599c307a9d10 .. notes/versioning�[39;49;00m
2022-08-01T23:23:09.2538155Z 
2022-08-01T23:23:09.2546088Z �[01mwaiting for workers...�[39;49;00m
2022-08-01T23:25:50.7294276Z /home/ec2-user/actions-runner/_work/_temp/246f077a-9fc7-4a64-ad2a-519aded78e81.sh: line 27: 14075 Killed                  docker exec -t "${container_name}" bash -c "sudo chown -R jenkins . && pip install dist/*.whl && ./.circleci/scripts/${DOCS_TYPE}_doc_push_script.sh"
2022-08-01T23:26:02.8045389Z ##[error]Process completed with exit code 137.
2022-08-01T23:26:02.9253089Z Prepare all required actions
2022-08-01T23:26:02.9373290Z ##[group]Run ./.github/actions/chown-workspace
2022-08-01T23:26:02.9373679Z ##[endgroup]
2022-08-01T23:26:02.9404273Z ##[group]Run docker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .
2022-08-01T23:26:02.9404920Z �[36;1mdocker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-08-01T23:26:02.9964040Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-08-01T23:26:02.9964426Z env:
2022-08-01T23:26:02.9964867Z   ALPINE_IMAGE: 308535385114.dkr.ecr.us-east-1.amazonaws.com/tool/alpine
2022-08-01T23:26:02.9965335Z ##[endgroup]
2022-08-01T23:26:03.4556269Z Unable to find image '308535385114.dkr.ecr.us-east-1.amazonaws.com/tool/alpine:latest' locally
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.

@Chillee
Copy link
Collaborator Author

Chillee commented Aug 1, 2022

@pytorchbot merge -g

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Aug 1, 2022

@pytorchbot successfully started a merge job. Check the current status here

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Aug 1, 2022

Merge failed due to Refusing to merge as mandatory check(s) pull failed for rule superuser
Raised by https://github.com/pytorch/pytorch/actions/runs/2778049562

@Chillee
Copy link
Collaborator Author

Chillee commented Aug 2, 2022

Was failing on master.

@Chillee
Copy link
Collaborator Author

Chillee commented Aug 2, 2022

@pytorchbot merge -f

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 2, 2022

❌ 🤖 pytorchbot command failed:

@pytorchbot merge: error: argument -f/--force: expected one argument

usage: @pytorchbot merge [-g | -f FORCE | -l]

Try @pytorchbot --help for more info.

@Chillee
Copy link
Collaborator Author

Chillee commented Aug 2, 2022

@pytorchbot merge -f "Failure is unrelated"

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Aug 2, 2022

@pytorchbot successfully started a merge job. Check the current status here

@github-actions
Copy link
Contributor

github-actions bot commented Aug 2, 2022

Hey @Chillee.
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.

facebook-github-bot pushed a commit to pytorch/functorch that referenced this pull request Aug 3, 2022
@Chillee @facebook-github-bot
guard against issues where we try to access tensor_meta on non-tensor…
4c6dc19 
… input (#82611) (#82611)

Summary:
X-link: pytorch/pytorch#82611
Approved by: https://github.com/voznesenskym

Reviewed By: kit1980

Differential Revision: D38359438

Pulled By: Chillee

fbshipit-source-id: 5fdefa57f93e5afc14f7f60e30a9ff35a9d4ee1c
facebook-github-bot pushed a commit that referenced this pull request Aug 3, 2022
@Chillee @facebook-github-bot
guard against issues where we try to access tensor_meta on non-tensor…
0a31dbf 
… input (#82611) (#82611)

Summary:
Pull Request resolved: #82611
Approved by: https://github.com/voznesenskym

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/c6b1e096afeabcc118c2e74db6709a1b4c531c53

Reviewed By: kit1980

Differential Revision: D38359438

Pulled By: Chillee

fbshipit-source-id: 5fdefa57f93e5afc14f7f60e30a9ff35a9d4ee1c
@facebook-github-bot facebook-github-bot deleted the gh/chillee/88/head branch August 5, 2022 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@voznesenskym voznesenskym voznesenskym approved these changes

Assignees

No one assigned

Labels

cla signed Merged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@Chillee @facebook-github-bot @pytorchmergebot @voznesenskym