Skip to content

Conversation

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 30, 2024

🔗 Helpful Links

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

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

⏳ No Failures, 147 Pending

As of commit ca05599 with merge base failed to retrieve merge base, please contact dev infra:
💚 Looks good so far! There are no failures yet. 💚

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

@pytorch-bot pytorch-bot bot added ciflow/inductor module: cpu CPU specific problem (e.g., perf, algorithm) release notes: fx release notes category labels Sep 30, 2024
@ezyang ezyang added the suppress-bc-linter Suppresses the failures of API backward-compatibility linter (Lint/bc_linter) label Sep 30, 2024
[ghstack-poisoned]
assert arg.fake_tensor is not None

def bind_symint(s, prop):
def bind_symint(s: torch.SymInt, prop):
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit specify return type

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There are actually a lot of untyped defs, I'm working on them in the next PR in stack

and raw_u1.args[0][0] == 1
and isinstance(eq := raw_u1.args[0][1], sympy.Eq)
and (
raw_u1_args0 := cast(
Copy link
Collaborator

Choose a reason for hiding this comment

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

We need casting? We can't just specify the type here before the walrus op?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Unfortunately, sympy annotates the type of args as Sequence[sympy.Basic], so the type annotation of args[0] is Basic when it needs to be a Tuple (because Piecewise). So even if we specified the type in walrus we would need to also do a mypy ignore.

[ghstack-poisoned]
@ezyang
Copy link
Contributor Author

ezyang commented Sep 30, 2024

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 1 checks: Lint / Test run_test.py is usable without boto3/rockset

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

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: inductor-periodic / cuda12.1-py3.10-gcc9-sm80 / test (inductor_torchbench_smoketest_perf, 1, 1, linux.gcp.a100)

Details for Dev Infra team Raised by workflow job

@ezyang
Copy link
Contributor Author

ezyang commented Sep 30, 2024

@pytorchbot merge -f "looks good"

@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

@ezyang
Copy link
Contributor Author

ezyang commented Sep 30, 2024

@pytorchbot merge -c nosignal -m "need to back out for merge conflict"

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 30, 2024

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: unrecognized arguments: -c nosignal -m need to back out for merge conflict

usage: @pytorchbot [-h] {merge,revert,rebase,label,drci,cherry-pick,close} ...

Try @pytorchbot --help for more info.

@ezyang
Copy link
Contributor Author

ezyang commented Sep 30, 2024

@pytorchbot revert -c nosignal -m "need to back out for merge conflict"

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

pytorchmergebot added a commit that referenced this pull request Sep 30, 2024
@pytorchmergebot
Copy link
Collaborator

@ezyang your PR has been successfully reverted.

[ghstack-poisoned]
AnantGulati pushed a commit to AnantGulati/pytorch that referenced this pull request Oct 2, 2024
@github-actions github-actions bot deleted the gh/ezyang/2948/head branch November 3, 2024 02:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request Merged module: cpu CPU specific problem (e.g., perf, algorithm) module: dynamo module: inductor release notes: fx release notes category Reverted suppress-bc-linter Suppresses the failures of API backward-compatibility linter (Lint/bc_linter)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants