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

[v.1.10.0] Release Tracker #65438

Closed
malfet opened this issue Sep 21, 2021 · 45 comments
Closed

[v.1.10.0] Release Tracker #65438

malfet opened this issue Sep 21, 2021 · 45 comments
Labels
oncall: releng In support of CI and Release Engineering triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Milestone

Comments

@malfet
Copy link
Contributor

malfet commented Sep 21, 2021

We cut a release branch for the 1.10.0 release.

Our plan from this point from this point is roughly:

  • Phase 1 (until 10/7): work on finalizing the release branch
  • Phase 2 (after 10/7): perform extended integration/stability/performance testing based on Release Candidate builds.

This issue is for tracking cherry-picks to the release branch.

Cherry-Pick Criteria

Phase 1 (until 10/7/21):

Only low-risk changes may be cherry-picked from master:

  1. Fixes to regressions against the most recent minor release (e.g. 1.9 for 1.10 release; see module: regression issue list)
  2. Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
  3. Fixes to new features introduced in the most recent minor release (e.g. 1.9.1 for 1.10 release)
  4. Test/CI fixes
  5. Documentation improvements
  6. Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
  7. Release branch specific changes (e.g. change version identifiers)

Any other change requires special dispensation from the release managers (currently @malfet, @seemethere, @gchanan, @zhouzhuojie ). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.

Phase 2 (after 10/7/21):

Note that changes here require us to rebuild a Release Candidate and restart extended testing (likely delaying the release). Therefore, the only accepted changes are Release-blocking critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks

Changes will likely require a discussion with the larger release team over VC or Slack.

Cherry-Pick Process

  1. Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).

  2. Create (but do not land) a PR against the release branch.

    # Find the hash of the commit you want to cherry pick
    # (for example, abcdef12345)
    git log
    
    git fetch origin release/1.10
    git checkout release/1.10
    git cherry-pick abcdef12345
    
    # Submit a PR based against 'release/1.10' either:
    # via the GitHub UI
    git push my-fork
    
    # via the GitHub CLI
    gh pr create --base release/1.10
  3. Make a request below with the following format:

Link to landed master PR (if applicable):
Link to release branch PR:
Criteria Category:
  1. Someone from the release team will reply with approved / denied or ask for more information.
  2. If approved, someone from the release team will merge your PR once the tests pass. Do not land the release branch PR yourself.

NOTE: Our normal tools (ghstack / ghimport, etc.) do not work on the release branch.

See HUD 1.10 or #65434 for release branch CI status

@malfet malfet added oncall: releng In support of CI and Release Engineering triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module labels Sep 21, 2021
@malfet malfet added this to the 1.10.0 milestone Sep 21, 2021
@malfet
Copy link
Contributor Author

malfet commented Sep 21, 2021

Link to landed master PR (if applicable): N/A
Link to release branch PR: #65433
Criteria Category: Releng


@malfet: merged

@zhouzhuojie zhouzhuojie pinned this issue Sep 22, 2021
@zou3519
Copy link
Contributor

zou3519 commented Sep 22, 2021

Link to landed master PR (if applicable): n/a
Link to release branch PR: #65496
Criteria Category: Release branch specific changes (removing prototype features not ready for release)


@malfet: merged

@malfet
Copy link
Contributor Author

malfet commented Sep 24, 2021

1.10.0-rc1 build is here
0.11.0-rc1 build of torchvision is here

@prabhat00155
Copy link
Contributor

prabhat00155 commented Sep 28, 2021

Link to landed master PR (if applicable): #65495 + #65921
Link to release branch PR: #65755
Criteria Category: 2


@malfet: [edit] After further discussion, reverted as feature work by #66308

@zhouzhuojie
Copy link
Contributor

Link to landed master PR: N/A
Link to release branch PR: #65787
Criteria Category: 4


@zhouzhuojie: merged

@prabhat00155
Copy link
Contributor

Link to landed master PR (if applicable): #65495 Link to release branch PR: #65755 Criteria Category: 2

@malfet: This does not look like a regression/backward compatibility fix, but a bit more like a feature work: as PR adds new argument to torch.optim.AveragedModel class

AveragedModel's update_parameter() doesn't update the parameters correctly in certain cases. This PR fixes that. Look at #65495 (comment) and #65495 (review) for more details.

@malfet
Copy link
Contributor Author

malfet commented Sep 29, 2021

Link to landed master PR: #65721
Link to release branch PR: #65835
Criteria Category: Performance regression from previous PR


@malfet: merged

@ejguan
Copy link
Contributor

ejguan commented Sep 30, 2021

Link to landed master PR: #65220
Link to release branch PR: #65924
Criteria Category: Fixes to new features introduced in the most recent minor release (e.g. 1.9.1 for 1.10 release) #64951


@malfet: merged

@ejguan
Copy link
Contributor

ejguan commented Sep 30, 2021

Link to landed master PR: #63646
Link to release branch PR: #65926
Criteria Category: Fixes to regressions against the most recent minor release (#63609)

Gentle ping to get this PR landed into release before branch cut: @malfet


@malfet: merged

@NivekT
Copy link
Contributor

NivekT commented Sep 30, 2021

Link to landed master PR: #65424, #65827, #65877
Link to release branch PR: #65932
Criteria Category: Fixes to regressions against the most recent minor release


@malfet: merged

@garymm
Copy link
Collaborator

garymm commented Oct 1, 2021

Link to landed master PR: #64370 #64371 #64373 #64380 #64382
Link to release branch PR: #65962
Criteria Category: Special Dispensation for ONNX-only changes


@malfet: merged

@malfet
Copy link
Contributor Author

malfet commented Oct 1, 2021

Link to landed master PR: #65934
Link to release branch PR: #65979
Criteria Category: CI fixes


@malfet: merged

@n-v-k
Copy link
Contributor

n-v-k commented Oct 5, 2021

Link to landed master PR: #66031
Link to release branch PR: #66117
Criteria Category: 6


@malfet: merged

@malfet
Copy link
Contributor Author

malfet commented Oct 5, 2021

Link to the landed master PR: #65444
Link to the release branch PR: #66155
Criteria Category: Regressions against the most recent minor release


@malfet: merged

@stas00
Copy link
Contributor

stas00 commented Oct 5, 2021

a likely regression - not triaged - #66086

@Jianhui-Li
Copy link

Jianhui-Li commented Oct 5, 2021

Hi, we would like to get Intel Extension to Pytorch tutorial into 1.10 release. Could you please merge it in?

@vitaly-fedyunin and @gottbrath give me this link.

Thanks. @malfet

@malfet
Copy link
Contributor Author

malfet commented Oct 6, 2021

a likely regression - not triaged - #66086

This issue is already have 1.10 milestone

@malfet
Copy link
Contributor Author

malfet commented Oct 6, 2021

Hi, we would like to get Intel Extension to Pytorch tutorial into 1.10 release. Could you please merge it in?

@vitaly-fedyunin and @gottbrath give me this link.

Thanks. @malfet

@Jianhui-Li can you please share link to the PR? Has it been merged into the main branch yet?

@malfet
Copy link
Contributor Author

malfet commented Oct 6, 2021

Link to the landed master PR: N/A
Link to the release branch PR: #66186
Criteria category: Release specific CI fixes


@malfet: merged

@malfet
Copy link
Contributor Author

malfet commented Oct 6, 2021

Link to the landed master PR: #66004
Link to the release branch PR: #66188
Criteria category: CI fixes


@malfet: merged

@Jianhui-Li
Copy link

Hi, we would like to get Intel Extension to Pytorch tutorial into 1.10 release. Could you please merge it in?
@vitaly-fedyunin and @gottbrath give me this link.
Thanks. @malfet

@Jianhui-Li can you please share link to the PR? Has it been merged into the main branch yet?

Sorry to forget the link pytorch/tutorials#1702

@garymm
Copy link
Collaborator

garymm commented Oct 11, 2021

@garymm I’m a bit confused, are you asking to cherry pick anything?

No. @malfet told me this would be an appropriate place to provide the release notes. If another place is better let me know.

@ngimel
Copy link
Collaborator

ngimel commented Oct 12, 2021

release branch PR #66524
master branch PR #66463,
criteria: regression, fixes #65709


@malfet: merged

@anjali411
Copy link
Contributor

anjali411 commented Oct 13, 2021

Master branch PR
#63602, #66572
Release branch PR #66667
Criteria: bug fixes for conjugate view (beta in 1.10)


@malfet: merged

@anjali411
Copy link
Contributor

anjali411 commented Oct 13, 2021

Master branch PR: #66082 (commit hash: a82fcd3)

Release branch PR: #66642
Criteria: bug fixes for conjugate view (beta in 1.10)


@malfet: merged

@malfet
Copy link
Contributor Author

malfet commented Oct 14, 2021

Master branch PR: #66433
Release branch PR: #66629
Criteria category: crashes, regression from previous release, see #66433


@malfet: merged

@kiukchung
Copy link
Collaborator

kiukchung commented Oct 14, 2021

Link to landed master PR (if applicable): #66182
Link to release branch PR: #66662
Criteria Category: special dispensation (documentation improvements, fixes to regressions against the most recent minor release)


@malfet: merged

@imaginary-person
Copy link
Contributor

Sorry, but #66712 might be a blocking issue for the release. I had introduced a bug that I fixed in #66703. 😞
Essentially, PyTorch builder seems to be using gcc 7.3 on CentOS for building release binaries, such as the nightly releases.
However, gcc versions below 9 don't support some AVX512 intrinsics present in the codebase, so AVX512 ATen kernels aren't being compiled, but due to the aforementioned bug, the CPU Capability in torch config is being displayed as AVX512 on machines that support AVX512 instruction sets being used by ATen kernels.

@malfet
Copy link
Contributor Author

malfet commented Oct 15, 2021

Sorry, but #66712 might be a blocking issue for the release. I had introduced a bug that I fixed in #66703. 😞 Essentially, PyTorch builder seems to be using gcc 7.3 on CentOS for building release binaries, such as the nightly releases. However, gcc versions below 9 don't support some AVX512 intrinsics present in the codebase, so AVX512 ATen kernels aren't being compiled, but due to the aforementioned bug, the CPU Capability in torch config is being displayed as AVX512 on machines that support AVX512 instruction sets being used by ATen kernels.

Hmm, this is indeed unfortunate, but what's the performance impact? Are AVX2 or default kernels will be selected in that case?

@imaginary-person
Copy link
Contributor

Hmm, this is indeed unfortunate, but what's the performance impact? Are AVX2 or default kernels will be selected in that case?

AVX2

@malfet
Copy link
Contributor Author

malfet commented Oct 15, 2021

AVX2

In that case it does not sound like a release blocker: i.e. users would not benefit from AVX512 perf boost, but CPU performance would be no different (and sometimes faster), than in PyTorch-1.9.0

@imaginary-person
Copy link
Contributor

imaginary-person commented Oct 15, 2021

Thanks, @malfet! Yes, the primary issue is that without fixing the aforementioned bug, many users might be misled about the ATen CPU capability.

BTW, please confirm if it's possible to release another binary that also has AVX512 kernels.
If that's not an option, is it possible to release the next version with gcc version >= 9, so that ATen AVX512 kernels are included in binaries (by then, the community would've tested it on nightly releases)?
Thanks!

@jgong5
Copy link
Collaborator

jgong5 commented Oct 19, 2021

hi @malfet : about the AVX-512 support, since it is a major feature added after 1.9 by @imaginary-person , will you highlight it for the 1.10 release? If so, having it enabled by default in the 1.10 binary release sounds more reasonable?

@randolf-scholz
Copy link
Contributor

Did you guys just accidentally release 1.10? It can be installed through conda:

pytorch                       1.10.0     py3.6_cpu_0  pytorch             
pytorch                       1.10.0 py3.6_cuda10.2_cudnn7.6.5_0  pytorch             
pytorch                       1.10.0 py3.6_cuda11.1_cudnn8.0.5_0  pytorch             
pytorch                       1.10.0 py3.6_cuda11.3_cudnn8.2.0_0  pytorch             
pytorch                       1.10.0     py3.7_cpu_0  pytorch             
pytorch                       1.10.0 py3.7_cuda10.2_cudnn7.6.5_0  pytorch             
pytorch                       1.10.0 py3.7_cuda11.1_cudnn8.0.5_0  pytorch             
pytorch                       1.10.0 py3.7_cuda11.3_cudnn8.2.0_0  pytorch             
pytorch                       1.10.0     py3.8_cpu_0  pytorch             
pytorch                       1.10.0 py3.8_cuda10.2_cudnn7.6.5_0  pytorch             
pytorch                       1.10.0 py3.8_cuda11.1_cudnn8.0.5_0  pytorch             
pytorch                       1.10.0 py3.8_cuda11.3_cudnn8.2.0_0  pytorch             
pytorch                       1.10.0     py3.9_cpu_0  pytorch             
pytorch                       1.10.0 py3.9_cuda10.2_cudnn7.6.5_0  pytorch             
pytorch                       1.10.0 py3.9_cuda11.1_cudnn8.0.5_0  pytorch             
pytorch                       1.10.0 py3.9_cuda11.3_cudnn8.2.0_0  pytorch  

However, neither the releases page nor the 1.10.0 milestone nor the 1.10 release tracker nor pypi indicate the update shipped yet.

@seemethere seemethere modified the milestones: 1.10.0, 1.10.1 Oct 25, 2021
@pytorch pytorch locked as resolved and limited conversation to collaborators Oct 25, 2021
@seemethere seemethere modified the milestones: 1.10.1, 1.11.0, 1.10.0 Oct 25, 2021
@seemethere
Copy link
Member

Closing this issue since 1.10.0 has been released!

Thanks everyone in this thread for all of the contributions that made 1.10.0 happen!

@seemethere seemethere unpinned this issue Oct 25, 2021
@malfet
Copy link
Contributor Author

malfet commented Oct 25, 2021

Started another torchaudio build to account for missing cuda-113 windows binaries: https://app.circleci.com/pipelines/github/pytorch/audio/8064/workflows/3c737d4b-72fa-4bb1-b5c0-90fa0c82c21a

@malfet
Copy link
Contributor Author

malfet commented Oct 26, 2021

Started torchvision build to fix packaging problem for cuda-113 linux wheels:
https://app.circleci.com/pipelines/github/pytorch/vision/11853/workflows/8521dddf-27bd-4276-a42b-331bac97521b

@seemethere seemethere pinned this issue Feb 3, 2022
@seemethere seemethere unpinned this issue Feb 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
oncall: releng In support of CI and Release Engineering triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

No branches or pull requests