Skip to content

[1.10] Remove torch.vmap#65496

Merged
malfet merged 1 commit intopytorch:release/1.10from
zou3519:vmap_1_10
Sep 24, 2021
Merged

[1.10] Remove torch.vmap#65496
malfet merged 1 commit intopytorch:release/1.10from
zou3519:vmap_1_10

Conversation

@zou3519
Copy link
Copy Markdown
Contributor

@zou3519 zou3519 commented Sep 22, 2021

torch.vmap is a prototype feature and should not be in the stable
binary. This PR:

  • Removes the torch.vmap API
  • Removes the documentation entry for torch.vmap
  • Changes the vmap tests to use an internal API instead of torch.vmap.

Test Plan:

  • Tested locally (test_torch, test_autograd, test_type_hints, test_vmap),
    but also wait for CI.

Fixes #{issue number}

torch.vmap is a prototype feature and should not be in the stable
binary. This PR:
- Removes the torch.vmap API
- Removes the documentation entry for torch.vmap
- Changes the vmap tests to use an internal API instead of torch.vmap.

Test Plan:
- Tested locally (test_torch, test_autograd, test_type_hints, test_vmap),
but also wait for CI.
@pytorch-probot
Copy link
Copy Markdown

CI Flow Status

⚛️ CI Flow

Ruleset - Version: v1
Ruleset - File: https://github.com/zou3519/pytorch/blob/9e9425b375181c86e717ba38e3f4c080ef1baa95/.github/generated-ciflow-ruleset.json
PR ciflow labels: ciflow/default

Workflows Labels (bold enabled) Status
Triggered Workflows
linux-bionic-py3.6-clang9 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/noarch, ciflow/xla ✅ triggered
linux-bionic-py3.8-gcc9-coverage ciflow/all, ciflow/coverage, ciflow/cpu, ciflow/default, ciflow/linux ✅ triggered
linux-xenial-cuda11.3-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/default, ciflow/linux ✅ triggered
linux-xenial-py3.6-gcc5.4 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux ✅ triggered
linux-xenial-py3.6-gcc7-bazel-test ciflow/all, ciflow/bazel, ciflow/cpu, ciflow/default, ciflow/linux ✅ triggered
win-vs2019-cpu-py3 ciflow/all, ciflow/cpu, ciflow/default, ciflow/win ✅ triggered
win-vs2019-cuda11.3-py3 ciflow/all, ciflow/cuda, ciflow/default, ciflow/win ✅ triggered
Skipped Workflows
libtorch-linux-xenial-cuda10.2-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux 🚫 skipped
libtorch-linux-xenial-cuda11.3-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux 🚫 skipped
linux-bionic-cuda10.2-py3.9-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/slow 🚫 skipped
linux-xenial-cuda10.2-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/slow 🚫 skipped
parallelnative-linux-xenial-py3.6-gcc5.4 ciflow/all, ciflow/cpu, ciflow/linux 🚫 skipped
periodic-libtorch-linux-xenial-cuda11.1-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/scheduled 🚫 skipped
periodic-linux-xenial-cuda11.1-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled 🚫 skipped
periodic-win-vs2019-cuda11.1-py3 ciflow/all, ciflow/cuda, ciflow/scheduled, ciflow/win 🚫 skipped
puretorch-linux-xenial-py3.6-gcc5.4 ciflow/all, ciflow/cpu, ciflow/linux 🚫 skipped
win-vs2019-cuda10.2-py3 ciflow/all, ciflow/cuda, ciflow/win 🚫 skipped

You can add a comment to the PR and tag @pytorchbot with the following commands:
# ciflow rerun, "ciflow/default" will always be added automatically
@pytorchbot ciflow rerun

# ciflow rerun with additional labels "-l <ciflow/label_name>", which is equivalent to adding these labels manually and trigger the rerun
@pytorchbot ciflow rerun -l ciflow/scheduled -l ciflow/slow

For more information, please take a look at the CI Flow Wiki.

@facebook-github-bot
Copy link
Copy Markdown
Contributor

facebook-github-bot commented Sep 22, 2021

🔗 Helpful links

💊 CI failures summary and remediations

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


  • 2/4 failures introduced in this PR
  • 2/4 broken upstream at merge base ad22804 on Sep 22 from 11:01am to 2:51pm

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages:

See GitHub Actions build linux-xenial-cuda11.3-py3.6-gcc7 / test (default, 1, 2, linux.8xlarge.nvidia.gpu) (1/1)

Step: "Unknown" (full log | diagnosis details | 🔁 rerun)

2021-09-23T01:52:19.4699245Z test_add_done_ca...arg() takes 0 positional arguments but 1 was given
2021-09-23T01:52:19.4668558Z   /opt/conda/lib/python3.6/unittest/suite.py(122): run
2021-09-23T01:52:19.4669676Z   /opt/conda/lib/python3.6/unittest/suite.py(84): __call__
2021-09-23T01:52:19.4670659Z   /opt/conda/lib/python3.6/site-packages/xmlrunner/runner.py(66): run
2021-09-23T01:52:19.4671444Z   /opt/conda/lib/python3.6/unittest/main.py(256): runTests
2021-09-23T01:52:19.4672152Z   /opt/conda/lib/python3.6/unittest/main.py(95): __init__
2021-09-23T01:52:19.4673179Z   /opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_utils.py(605): run_tests
2021-09-23T01:52:19.4673973Z   test_futures.py(329): <module>
2021-09-23T01:52:19.4674321Z 
2021-09-23T01:52:19.4674762Z ok (0.002s)
2021-09-23T01:52:19.4692061Z   test_add_done_callback_maintains_callback_order (__main__.TestFuture) ... ok (0.003s)
2021-09-23T01:52:19.4699245Z   test_add_done_callback_no_arg_error_is_ignored (__main__.TestFuture) ... [E pybind_utils.h:201] Got the following error when running the callback: TypeError: no_arg() takes 0 positional arguments but 1 was given
2021-09-23T01:52:19.4700603Z ok (0.001s)
2021-09-23T01:52:19.4712744Z   test_add_done_callback_simple (__main__.TestFuture) ... ok (0.001s)
2021-09-23T01:52:19.4757073Z   test_chained_then (__main__.TestFuture) ... ok (0.004s)
2021-09-23T01:52:19.5782599Z   test_collect_all (__main__.TestFuture) ... ok (0.102s)
2021-09-23T01:52:19.5792688Z   test_done (__main__.TestFuture) ... ok (0.001s)
2021-09-23T01:52:19.5808192Z   test_done_exception (__main__.TestFuture) ... ok (0.001s)
2021-09-23T01:52:19.5827731Z   test_interleaving_then_and_add_done_callback_maintains_callback_order (__main__.TestFuture) ... ok (0.002s)
2021-09-23T01:52:19.5840514Z   test_interleaving_then_and_add_done_callback_propagates_error (__main__.TestFuture) ... [E pybind_utils.h:201] Got the following error when running the callback: ValueError: Expected error
2021-09-23T01:52:19.5841756Z 
2021-09-23T01:52:19.5842111Z At:

1 failure not recognized by patterns:

Job Step Action
GitHub Actions linux-xenial-py3.6-gcc5.4 / build-docs (cpp) Unknown 🔁 rerun

🚧 2 fixed upstream failures:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@codecov
Copy link
Copy Markdown

codecov bot commented Sep 23, 2021

Codecov Report

Merging #65496 (9e9425b) into release/1.10 (ad22804) will decrease coverage by 1.41%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           release/1.10   #65496      +/-   ##
================================================
- Coverage         66.38%   64.97%   -1.42%     
================================================
  Files               738      738              
  Lines             94182    94181       -1     
================================================
- Hits              62522    61193    -1329     
- Misses            31660    32988    +1328     

Copy link
Copy Markdown
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

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

LGTM

@malfet malfet merged commit 0e857bf into pytorch:release/1.10 Sep 24, 2021
zou3519 added a commit that referenced this pull request Feb 3, 2022
torch.vmap is a prototype feature and should not be in the stable
binary. This PR:
- Removes the torch.vmap API
- Removes the documentation entry for torch.vmap
- Changes the vmap tests to use an internal API instead of torch.vmap.

Test Plan:
- Tested locally (test_torch, test_autograd, test_type_hints, test_vmap),
but also wait for CI.
malfet pushed a commit that referenced this pull request Feb 4, 2022
* release 1.11 Install torch from test channel, Pin builder and xla repo (#72217)

* [1.11] Remove torch.vmap (#65496)

torch.vmap is a prototype feature and should not be in the stable
binary. This PR:
- Removes the torch.vmap API
- Removes the documentation entry for torch.vmap
- Changes the vmap tests to use an internal API instead of torch.vmap.

Test Plan:
- Tested locally (test_torch, test_autograd, test_type_hints, test_vmap),
but also wait for CI.

Co-authored-by: Andrey Talman <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants