Skip to content

Conversation

@ezyang
Copy link
Contributor

@ezyang ezyang commented Sep 25, 2024

Stack from ghstack (oldest at bottom):

Instead, callback to a missing handler when needed. This greatly speeds things up with the value ranges dict is large. The missing handler is needed because nested ints don't have VRs, but symbolic sizes involving them occasionally show up in compute.

TORCHDYNAMO_EXTENDED_DEBUG_CREATE_SYMBOL="s11" TORCH_LOGS=dynamic PYTORCH_TEST_WITH_DYNAMO=1 python test/test_nestedtensor.py TestNestedTensorAutogradCPU.test_dropout_backward_jagged_cpu

Signed-off-by: Edward Z. Yang [email protected]

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 25, 2024

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit e0ed5b5 with merge base 59cdd8d (image):

NEW FAILURE - The following job has failed:

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

@pytorch-bot pytorch-bot bot added module: cpu CPU specific problem (e.g., perf, algorithm) labels Sep 25, 2024
@ezyang ezyang added the topic: not user facing topic category label Sep 25, 2024
[ghstack-poisoned]
ezyang added a commit that referenced this pull request Sep 25, 2024
My first plan is to fix all symbol allocation sites to correctly add
value ranges.  My second plan is to push it into bound_sympy itself (a
default value).

Signed-off-by: Edward Z. Yang <[email protected]>

ghstack-source-id: b230af7
Pull Request resolved: #136667
@ezyang ezyang requested a review from jbschlosser September 25, 2024 21:13
@ezyang ezyang added the ciflow/trunk Trigger trunk jobs on your pull request label Sep 25, 2024
Copy link
Collaborator

@isuruf isuruf left a comment

Choose a reason for hiding this comment

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

Minor nitpick

[ghstack-poisoned]
ezyang added a commit that referenced this pull request Sep 26, 2024
My first plan is to fix all symbol allocation sites to correctly add
value ranges.  My second plan is to push it into bound_sympy itself (a
default value).

Signed-off-by: Edward Z. Yang <[email protected]>

ghstack-source-id: f91a61c
Pull Request resolved: #136667
@albanD albanD removed their request for review October 4, 2024 19:17
@isuruf isuruf mentioned this pull request Oct 7, 2024
@ezyang
Copy link
Contributor Author

ezyang commented Oct 8, 2024

@pytorchbot merge -r

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[ghstack-poisoned]
pytorchmergebot pushed a commit that referenced this pull request Oct 8, 2024
My first plan is to fix all symbol allocation sites to correctly add
value ranges.  My second plan is to push it into bound_sympy itself (a
default value).

Signed-off-by: Edward Z. Yang <[email protected]>

ghstack-source-id: 61e1130
Pull Request resolved: #136667
@pytorchmergebot
Copy link
Collaborator

Successfully rebased gh/ezyang/2941/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/136667)

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@ezyang
Copy link
Contributor Author

ezyang commented Oct 8, 2024

@pytorchbot merge -f "xla failure is fake"

@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

@github-actions github-actions bot deleted the gh/ezyang/2941/head branch November 8, 2024 02:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request Merged module: cpu CPU specific problem (e.g., perf, algorithm) topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants