KEMBAR78
Make ValueRange repr less chatty by default by ezyang · Pull Request #128043 · pytorch/pytorch · GitHub
Skip to content

Conversation

@ezyang
Copy link
Contributor

@ezyang ezyang commented Jun 5, 2024

[ghstack-poisoned]
@pytorch-bot pytorch-bot bot added the module: cpu CPU specific problem (e.g., perf, algorithm) label Jun 5, 2024
@pytorch-bot
Copy link

pytorch-bot bot commented Jun 5, 2024

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 1 New Failure, 7 Unrelated Failures

As of commit 29acbb9 with merge base f08fd8e (image):

NEW FAILURE - The following job has failed:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

BROKEN TRUNK - The following jobs failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:

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

[ghstack-poisoned]
ezyang added a commit that referenced this pull request Jun 5, 2024
Signed-off-by: Edward Z. Yang <ezyang@meta.com>

ghstack-source-id: bb92f38
Pull Request resolved: #128043
Copy link
Collaborator

@lezcano lezcano left a comment

Choose a reason for hiding this comment

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

<3

@lezcano
Copy link
Collaborator

lezcano commented Jun 5, 2024

lint is complaining tho

[ghstack-poisoned]
ezyang added a commit that referenced this pull request Jun 6, 2024
Signed-off-by: Edward Z. Yang <ezyang@meta.com>

ghstack-source-id: 9110663
Pull Request resolved: #128043
@lezcano
Copy link
Collaborator

lezcano commented Jun 6, 2024

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jun 6, 2024
@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: Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x 2f4e8712ec1c65e60a2f1610d86e35d4d45bd8ec returned non-zero exit code 1

Auto-merging test/dynamo/test_misc.py
CONFLICT (content): Merge conflict in test/dynamo/test_misc.py
Auto-merging torch/utils/_sympy/value_ranges.py
error: could not apply 2f4e8712ec1... Make ValueRange repr less chatty by default
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Details for Dev Infra team Raised by workflow job

[ghstack-poisoned]
ezyang added a commit that referenced this pull request Jun 6, 2024
Signed-off-by: Edward Z. Yang <ezyang@meta.com>

ghstack-source-id: 9f95d84
Pull Request resolved: #128043
@ezyang
Copy link
Contributor Author

ezyang commented Jun 6, 2024

@pytorchbot merge -f "ci failures look unrelated"

@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

@atalman
Copy link
Contributor

atalman commented Jun 7, 2024

@pytorchmergebot revert -c ghfirst -m "Sorry reverting because in conflict with #126905 which needs to be reverted"

@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
Copy link
Collaborator

@ezyang your PR has been successfully reverted.

pytorchmergebot added a commit that referenced this pull request Jun 7, 2024
This reverts commit f0dd11d.

Reverted #128043 on behalf of https://github.com/atalman due to Sorry reverting because in conflict with [#126905](#126905) which needs to be reverted ([comment](#128043 (comment)))
@atalman
Copy link
Contributor

atalman commented Jun 7, 2024

@pytorchmergebot rebase -b main

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Rebase failed due to

Aborting rebase because rebasing the branch resulted in the same sha as the target branch.
This usually happens because the PR has already been merged.  Please rebase locally and push.

Raised by https://github.com/pytorch/pytorch/actions/runs/9419893823

@ezyang ezyang closed this Jun 10, 2024
TharinduRusira pushed a commit to TharinduRusira/pytorch that referenced this pull request Jun 14, 2024
Signed-off-by: Edward Z. Yang <ezyang@meta.com>

Pull Request resolved: pytorch#128043
Approved by: https://github.com/lezcano
TharinduRusira pushed a commit to TharinduRusira/pytorch that referenced this pull request Jun 14, 2024
This reverts commit f0dd11d.

Reverted pytorch#128043 on behalf of https://github.com/atalman due to Sorry reverting because in conflict with [pytorch#126905](pytorch#126905) which needs to be reverted ([comment](pytorch#128043 (comment)))
@github-actions github-actions bot deleted the gh/ezyang/2801/head branch July 10, 2024 16:24
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) module: dynamo release notes: dynamo Reverted

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants