Skip to content

Rewrite upgrader bytecode version from 3 to 4 (content unchanged) #75120

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Rewrite upgrader bytecode version from 3 to 4 (content unchanged) #75120

wants to merge 1 commit into from

Conversation

cccclai
Copy link
Contributor

@cccclai cccclai commented Apr 1, 2022 •
edited
Loading

@facebook-github-bot
Copy link
Contributor

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

🔗 Helpful links

💊 CI failures summary and remediations

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

💚 💚 Looks good so far! There are no failures yet. 💚 💚

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.

@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Apr 1, 2022
This was referenced Apr 1, 2022
Closed
Closed
facebook-github-bot pushed a commit that referenced this pull request Apr 2, 2022
@cccclai @facebook-github-bot
Rewrite upgrader bytecode version from 3 to 4 (content unchanged) (#7…
74bb2da 
…5120)

Summary:
update the upgrader models by hacking backport logic - copy everything in the model and only rewrite the bytecode version to 4 in D35265596

Pull Request resolved: #75120

ghstack-source-id: 152823046

Test Plan: CI

Reviewed By: qihqi

Differential Revision: D35321154

fbshipit-source-id: 333158bd0fd9b4819b3b7cf47d80c285934adf3e
@github-actions
Copy link
Contributor

github-actions bot commented Apr 2, 2022

Hey @cccclai.
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 facebook-github-bot deleted the gh/cccclai/166/head branch April 5, 2022 14:17
NesrineMHB pushed a commit to NesrineMHB/pytorch that referenced this pull request Apr 8, 2022
Rewrite upgrader bytecode version from 3 to 4 (content unchanged)
ca2fbbe 
Differential Revision: [D35321154](https://our.internmc.facebook.com/intern/diff/D35321154/)

ghstack-source-id: 152823046
Pull Request resolved: pytorch/pytorch#75120
@WBobby WBobby mentioned this pull request Aug 17, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
cla signed oncall: jit Add this issue/PR to JIT oncall triage queue
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@cccclai @facebook-github-bot