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

[v1.5.0] Release Tracker #35009

Closed
gchanan opened this issue Mar 19, 2020 · 72 comments
Closed

[v1.5.0] Release Tracker #35009

gchanan opened this issue Mar 19, 2020 · 72 comments
Labels
triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Milestone

Comments

@gchanan
Copy link
Contributor

gchanan commented Mar 19, 2020

The 1.5 release branch has been cut!

This issue is for tracking cherry-picks to the release branch. The criteria for a change to be included is ALL of the following:

  1. bug fix or documentation fix/improvement (i.e. NOT a feature)
  2. already landed in master or specific to 1.5 (e.g. deprecating a feature in 1.5)
  3. worth the risk/reward. For example, a large change that fixes a tiny bug would not be included.

If you need a change to be cherry-picked to the branch, please open a PR against the release/1.5 branch and comment below. Any details you can provide about the criteria above (e.g. links to master PR, description of the severity of the bug fix) are helpful. Ultimately we will make an inclusion / no inclusion call and communicate that here.

NOTE: do not land the PRs yourself. Our normal tools (ghstack / ghimport, etc.) do not work on the release branch. Someone else will land your change for you.


Current PRs open against the release/1.5

@gchanan gchanan pinned this issue Mar 19, 2020
@jamesr66a
Copy link
Collaborator

jamesr66a commented Mar 19, 2020

Docs change once it lands #35007

EDIT: release/1.5 PR #35043


This was included when we fast forwarded the release branch.

@VitalyFedyunin VitalyFedyunin added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Mar 19, 2020
@VitalyFedyunin
Copy link
Contributor

VitalyFedyunin commented Mar 19, 2020

#34934 fixes of maxpool (somehow didn't make it into release cut)


This was included when we fast forwarded the release branch.

@gchanan
Copy link
Contributor Author

gchanan commented Mar 19, 2020

@jamesr66a: looks good to go, can you open a PR against the release branch?

@mcarilli
Copy link
Collaborator

mcarilli commented Mar 19, 2020

#35340 may be a candidate. Autocasting completes Pytorch's native automatic mixed precision support, which I've been writing for over 6 months now targeting 1.5. It has thorough documentation and test coverage. It was approved and merged already, but reverted for minor fixes.

Update: PR against master #35102 has been re-merged and stuck the landing so far. #35340 cherry-picks those diffs onto 1.5 (+3 lines of cosmetic docstring changes).


Feature, sorry :(. It's in nightlies though.

@seemethere seemethere added this to the 1.5.0 milestone Mar 19, 2020
@yf225
Copy link
Contributor

yf225 commented Mar 20, 2020

C++ frontend fixes:

Cherry-picked into 1.5:


Merged

@jamesr66a
Copy link
Collaborator

jamesr66a commented Mar 20, 2020

#35133

^We'd like to get this in because it aligns torchbind's qualified names with the custom op API, and sets us up to converge the two in the future. Getting this into 1.5 would allow us to save a lot of BC headache in the future

EDIT: Was reverted. Will update with superseding PR soon
EDIT2: Updated PR #35303


Merged

@zasdfgbnm
Copy link
Collaborator

zasdfgbnm commented Mar 21, 2020

#35146

^ Docs fix of DP vs DDP on CUDA


Merged

@prajjwal1
Copy link
Contributor

prajjwal1 commented Mar 23, 2020

Leaving it here because this PR fixes a high priority issue. This PR adds Support for Tensor Shape Type Hint.


This made the release branch.

@seemethere
Copy link
Member

seemethere commented Mar 23, 2020

#35242

^ Script fix to unblock all of CI


Merged

@peterjc123
Copy link
Collaborator

peterjc123 commented Mar 24, 2020

#35275

^ Load torch_global_deps for Windows

EDIT: Was abandoned. Will update with superseding PR soon


Abandoned

@seemethere
Copy link
Member

seemethere commented Mar 24, 2020

#35310

^ Switching default CUDA to 10.2 for wheels


Merged

@ailzhang
Copy link
Contributor

ailzhang commented Mar 24, 2020

#35315

Pin XLA CI to use r1.5 release branch.


merged

@mruberry
Copy link
Collaborator

mruberry commented Mar 24, 2020

#35321, required for porting #34794, the latter of which will let users workaround torch.div using either torch.floor_divide or torch.true_divide as appropriate.


Merged

@peterjc123
Copy link
Collaborator

peterjc123 commented Mar 25, 2020

#35368

^ Load all DLLs in the lib directory for Windows


Merged

@mrshenli
Copy link
Contributor

mrshenli commented Mar 25, 2020

Ready patches for PTD:

#35262 #35514 enforce rref JIT pickling to be in the scope of rpc calls (port for #34689)
#35264 #35513 Enforce rref python pickling to be in the scope of RPC call (port for #34755)

WIP doc patches for PTD:

#35109 Refactored rpc docs (will need a new PR against release/1.5 after land to master)


Merged non-WIP patches.

cc @zhaojuanmao @rohan-varma

@mruberry
Copy link
Collaborator

mruberry commented Mar 25, 2020

#35390, which ports #34794, which adds a torch.true_divide method variant. This lets users workaround torch.div using either torch.floor_divide or torch.true_divide in all scenarios.


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Mar 25, 2020

#35349 was opened as a port for #35144.


Merged.

@mrshenli
Copy link
Contributor

mrshenli commented Mar 25, 2020

#35402 Fix RPC test_torchscript_functions_not_supported failure on the release branch. (port for #35283)

cc @xush6528


Merged

@ailzhang
Copy link
Contributor

ailzhang commented Mar 25, 2020

[doc]Updating view op list #35403


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Mar 25, 2020

#35406, port of #35131.
#35405, port of #35231.
#35407, port of #35053.


Merged all.

@seemethere
Copy link
Member

seemethere commented Mar 25, 2020

#35412

^ To add future as a dependency for all of our packages


Merged

@houseroad
Copy link
Member

houseroad commented Mar 25, 2020

#35413 bump up ONNX exporter's version (original: #35059)

#35416 fix torch.mm in ONNX exporter (original: #34661)


Merged

@VitalyFedyunin
Copy link
Contributor

VitalyFedyunin commented Mar 25, 2020

#35434 contains doc strings and documentation updates for channels last


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Mar 26, 2020

#35435, port of #35253.


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Mar 26, 2020

#35436, port of #34822.


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Mar 26, 2020

#35477, port of #35150.


Merged.

@ailzhang
Copy link
Contributor

ailzhang commented Mar 27, 2020

#35450 , adding a warning for a known autograd issue in XLA backend.


Merged

@jlin27
Copy link
Contributor

jlin27 commented Apr 7, 2020

#36165

Group libraries in docs table of contents and add link to new PyTorch Elastic page


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Apr 7, 2020

#36185, port of 35984.


Merged

@yf225
Copy link
Contributor

yf225 commented Apr 8, 2020

#36245, port of #36161 C++ Adam optimizer - corrected messages for check of default options.


Merged

@yf225
Copy link
Contributor

yf225 commented Apr 9, 2020

#36274, port of #35601 fix is_float_scale_factor warning (python and c++)


Merged

@bmanga
Copy link

bmanga commented Apr 10, 2020

Not sure if this is the right place, but I would consider issue #36378 to be a blocker for release, as for example it prevents building torchvision.

@zhaojuanmao zhaojuanmao unpinned this issue Apr 10, 2020
@gchanan gchanan pinned this issue Apr 13, 2020
@mcarilli
Copy link
Collaborator

mcarilli commented Apr 13, 2020

#36514

minor change to fix formatting errors in the warnings added by #35745.


Merged

@erip
Copy link
Contributor

erip commented Apr 14, 2020

Any possibility of sneaking #35352 into 1.5.0?


Nope, feature.

@lucasjinreal
Copy link

AT_CHECK is gone, what's alternative?

@mrshenli
Copy link
Contributor

mrshenli commented Apr 15, 2020

#36537, port of #36656

Add a warning for Single-Process Multi-GPU DDP


Merged

@mrshenli
Copy link
Contributor

AT_CHECK is gone, what's alternative?

@jinfagang TORCH_CHECK is the alternative.

@gchanan
Copy link
Contributor Author

gchanan commented Apr 15, 2020

Any possibility of sneaking #35352 into 1.5.0?

No, this is a feature.

@peterjc123
Copy link
Collaborator

peterjc123 commented Apr 16, 2020

#36658 Migrate release CI jobs to CircleCI for Windows (v1.5 Release)


Merged

@mrshenli
Copy link
Contributor

mrshenli commented Apr 16, 2020

#36732, port of #36675

Doc-only change to make sure existing URLs to RPC docs are still valid.


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Apr 17, 2020

#36782, port of #36780.


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Apr 17, 2020

#36762, port of #36760.


Merged

@gchanan
Copy link
Contributor Author

gchanan commented Apr 17, 2020

#36761, port of #36736.


Merged

@Krovatkin
Copy link
Contributor

Krovatkin commented Apr 17, 2020

@gchanan

#36824

Given that we keep running into the issue of incredibly long compilation times, we decided to switch to the simple executor which skips fusion-related passes and analyses. It might affect some users that rely on fusion on GPU to achieve their performance. profile. We will make a note in our release notes for such users to enable the profiling executor.


Merged

@Roshrini
Copy link

@mrshenli Is this issue getting tracked for release? #36268
PR #36523

@mruberry
Copy link
Collaborator

mruberry commented Apr 17, 2020

#36839, which fixes #36798.


Didn't make it, documented in known issues.

@mrshenli
Copy link
Contributor

mrshenli commented Apr 20, 2020

disable flaky test #36924


Merged

@ailzhang
Copy link
Contributor

ailzhang commented Apr 20, 2020

#36927 fixes xla job failure on release/1.5 branch. (CI only change)


Merged

@Krovatkin
Copy link
Contributor

Krovatkin commented Apr 21, 2020

@gchanan #36933 should fix the test failures


Merged, but didn't make the RC. So if we do another release or RC it will be in, but otherwise we'll have some known test failures.

@mrshenli
Copy link
Contributor

mrshenli commented Apr 21, 2020

#36947, port for #36948

Fixes build error when USE_DISTRIBUTED=0. This does not need to be added into our release binaries as they are all built with USE_DISTRIBUTED=1, but needs to be landed into the release/1.5 source branch in case users would like to build using USE_DISTRIBUTED=0.


Didn't make it, this seems minor.

@gchanan
Copy link
Contributor Author

gchanan commented Apr 21, 2020

@mrshenli Is this issue getting tracked for release? #36268
PR #36523

No, we weren't confident in the fix so close to the release.

@gchanan gchanan closed this as completed Apr 29, 2020
@gchanan gchanan unpinned this issue Apr 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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