Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix 'Could not infer dtype of SymBool' on torch.tensor call #125656

Closed
wants to merge 2 commits into from

Conversation

[ghstack-poisoned]
Copy link

pytorch-bot bot commented May 7, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/125656

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 3 Unrelated Failures

As of commit 3a1e14c with merge base b6bcd09 (image):

NEW FAILURE - The following job has failed:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

ezyang added a commit that referenced this pull request May 7, 2024
Internal xref:
https://fb.workplace.com/groups/469587837192818/posts/1638909336927323/

Signed-off-by: Edward Z. Yang <ezyang@meta.com>

ghstack-source-id: 35488536dee6ce6c35497defde093b103fb967a2
Pull Request resolved: #125656
[ghstack-poisoned]
ezyang added a commit that referenced this pull request May 7, 2024
Internal xref:
https://fb.workplace.com/groups/469587837192818/posts/1638909336927323/

Signed-off-by: Edward Z. Yang <ezyang@meta.com>

ghstack-source-id: 133e960af8046ea627c86836aff866c5d0a7da06
Pull Request resolved: #125656
@ezyang ezyang added ciflow/trunk Trigger trunk jobs on your pull request topic: bug fixes topic category release notes: dynamo labels May 7, 2024
@ezyang
Copy link
Contributor Author

ezyang commented May 7, 2024

@pytorchbot merge -f "unrelated failures"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

huydhn added a commit to pytorch/test-infra that referenced this pull request May 9, 2024
This extends Dr.CI to handle disabled test issues in several cases:

1. The closing of disabled test issues whereas a test could start
failing on PR after its associated disabled issue is resolved.
2. A disabled test fails on PR where it should be skipped.

In both cases, the failure will be marked as skipped and the reason is
provided.

### Testing

pytorch/pytorch#125656

## ❌ 1 New Failure, 3 Unrelated Failures
As of commit 3a1e14cc5b5d44fa1b04561bccf14d832f70eb1d with merge base
b6bcd0917310c657fc60bc7b20415f6948524eb8 (<sub><sub><img alt="image"
width=70
src="https://img.shields.io/date/1715002918?label=&color=FFFFFF&style=flat-square"></sub></sub>):
<details open><summary><b>NEW FAILURE</b> - The following job has
failed:</summary><p>

* [pull / linux-focal-cuda12.1-py3.10-gcc9 / test (default, 5, 5,
linux.4xlarge.nvidia.gpu)](https://hud.pytorch.org/pr/pytorch/pytorch/125656#24661015414)
([gh](https://github.com/pytorch/pytorch/actions/runs/8979058478/job/24661015414))

`test_foreach.py::TestForeachCUDA::test_parity__foreach_abs_fastpath_inplace_cuda_complex128`
</p></details>
<details ><summary><b>FLAKY</b> - The following jobs failed but were
likely due to flakiness present on trunk:</summary><p>

* [trunk / linux-focal-cuda12.1-py3.10-gcc9 / test (nogpu_AVX512, 1, 1,
linux.2xlarge)](https://hud.pytorch.org/pr/pytorch/pytorch/125656#24687436887)
([gh](https://github.com/pytorch/pytorch/actions/runs/8987492536/job/24687436887))
(disabled by
[#104012](pytorch/pytorch#104012))
`test_fx.py::TestFXAPIBackwardCompatibility::test_public_api_surface`
* [trunk / linux-focal-cuda12.1-py3.10-gcc9 / test (nogpu_NO_AVX2, 1, 1,
linux.2xlarge)](https://hud.pytorch.org/pr/pytorch/pytorch/125656#24687437259)
([gh](https://github.com/pytorch/pytorch/actions/runs/8987492536/job/24687437259))
(disabled by
[#104012](pytorch/pytorch#104012))
`test_fx.py::TestFXAPIBackwardCompatibility::test_public_api_surface`
* [trunk / macos-12-py3-arm64 / test (default, 1, 3,
macos-m1-stable)](https://hud.pytorch.org/pr/pytorch/pytorch/125656#24686497666)
([gh](https://github.com/pytorch/pytorch/actions/runs/8987492536/job/24686497666))
(disabled by
[#104012](pytorch/pytorch#104012))
`test_fx.py::TestFXAPIBackwardCompatibility::test_public_api_surface`
</p></details>

pytorch/pytorch#125634

## ❌ 1 New Failure, 1 Unrelated Failure
As of commit 28cdf5b4af9803379b6206b8ffbdf214949f111b with merge base
22bcfc25ef3043db37e88ad61ba69c85f98571e1 (<sub><sub><img alt="image"
width=70
src="https://img.shields.io/date/1715033427?label=&color=FFFFFF&style=flat-square"></sub></sub>):
<details open><summary><b>NEW FAILURE</b> - The following job has
failed:</summary><p>

* [pull / linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default, 4, 5,
linux.g5.4xlarge.nvidia.gpu)](https://hud.pytorch.org/pr/pytorch/pytorch/125634#24685445893)
([gh](https://github.com/pytorch/pytorch/actions/runs/8986634257/job/24685445893))
([#98259](pytorch/pytorch#98259))
    `test_type_hints.py::TestTypeHints::test_doc_examples`
</p></details>
<details ><summary><b>FLAKY</b> - The following job failed but was
likely due to flakiness present on trunk:</summary><p>

* [pull / linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default, 1, 5,
linux.g5.4xlarge.nvidia.gpu)](https://hud.pytorch.org/pr/pytorch/pytorch/125634#24685444407)
([gh](https://github.com/pytorch/pytorch/actions/runs/8986634257/job/24685444407))
(disabled by
[#104012](pytorch/pytorch#104012))
`test_fx.py::TestFXAPIBackwardCompatibility::test_public_api_surface`
</p></details>
@github-actions github-actions bot deleted the gh/ezyang/2731/head branch June 7, 2024 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants