Skip to content

Conversation

@wconstab
Copy link
Contributor

@wconstab wconstab commented Apr 5, 2022

Stack from ghstack (oldest at bottom):

  • default to generating forced fallback for TS backend (where it is used
    for tests/debugging, but false otherwise

Differential Revision: D35411211

- default to generating forced fallback for TS backend (where it is used
for tests/debugging, but false otherwise

[ghstack-poisoned]
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Apr 5, 2022

🔗 Helpful links

💊 CI failures summary and remediations

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


  • 2/2 failures introduced in this PR

🕵️ 1 new failure recognized by patterns

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

See GitHub Actions build pull / linux-bionic-py3.7-clang9 / test (default, 2, 2, linux.2xlarge) (1/1)

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

2022-04-05T23:43:46.1491560Z test_add_done_ca...arg() takes 0 positional arguments but 1 was given
2022-04-05T23:43:46.1465124Z   /opt/conda/lib/python3.7/unittest/suite.py(122): run
2022-04-05T23:43:46.1465586Z   /opt/conda/lib/python3.7/unittest/suite.py(84): __call__
2022-04-05T23:43:46.1466198Z   /opt/conda/lib/python3.7/site-packages/xmlrunner/runner.py(67): run
2022-04-05T23:43:46.1466690Z   /opt/conda/lib/python3.7/unittest/main.py(271): runTests
2022-04-05T23:43:46.1467145Z   /opt/conda/lib/python3.7/unittest/main.py(101): __init__
2022-04-05T23:43:46.1467833Z   /opt/conda/lib/python3.7/site-packages/torch/testing/_internal/common_utils.py(682): run_tests
2022-04-05T23:43:46.1468297Z   test_futures.py(331): <module>
2022-04-05T23:43:46.1468484Z 
2022-04-05T23:43:46.1468596Z ok (0.201s)
2022-04-05T23:43:46.1484830Z   test_add_done_callback_maintains_callback_order (__main__.TestFuture) ... ok (0.002s)
2022-04-05T23:43:46.1491560Z   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
2022-04-05T23:43:46.1492512Z ok (0.001s)
2022-04-05T23:43:46.1503622Z   test_add_done_callback_simple (__main__.TestFuture) ... ok (0.001s)
2022-04-05T23:43:46.1542677Z   test_chained_then (__main__.TestFuture) ... ok (0.004s)
2022-04-05T23:43:46.2560242Z   test_collect_all (__main__.TestFuture) ... ok (0.102s)
2022-04-05T23:43:46.2567451Z   test_done (__main__.TestFuture) ... ok (0.001s)
2022-04-05T23:43:46.2579428Z   test_done_exception (__main__.TestFuture) ... ok (0.001s)
2022-04-05T23:43:46.2595525Z   test_interleaving_then_and_add_done_callback_maintains_callback_order (__main__.TestFuture) ... ok (0.002s)
2022-04-05T23:43:46.2605913Z   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
2022-04-05T23:43:46.2606777Z 
2022-04-05T23:43:46.2606896Z At:

🕵️‍♀️ 1 failure not recognized by patterns:

The following CI failures may be due to changes from the PR
Job Step Action
GitHub Actions pull / linux-bionic-rocm5.0-py3.7 / test (default, 2, 2, linux.rocm.gpu) Set up job 🔁 rerun

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.

@wconstab wconstab requested review from JackCaoG and bdhirsh April 5, 2022 19:50
Copy link
Collaborator

@JackCaoG JackCaoG left a comment

Choose a reason for hiding this comment

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

Thanks!

Copy link
Collaborator

@antoniojkim antoniojkim left a comment

Choose a reason for hiding this comment

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

Thanks for this!

per_operator_headers: bool = False,
backend_name: str = default_args.backend_name) -> None:
backend_name: str = default_args.backend_name,
gen_forced_fallback_code: bool = False) -> None:
Copy link
Contributor

Choose a reason for hiding this comment

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

mostly just to make sure i'm following along - doesn't this path only get taken at runtime if an environment variable is set? I'm wondering if there's any reason to make it conditional in the codegen instead of just being conditional on the env variable.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree with you, but Jack was wanting cleaner generated code; I think we could convince him to accept it, but there was one particular issue:

the header ts_eager_fallback.h needed to be included if that code is generated, so using this flag in the codegen lets us skip including that header. If in the future we make the fallback part of the backend-api, we could consider always generating this codepath.

Copy link
Contributor

Choose a reason for hiding this comment

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

ok, sounds reasonable. The delta is super small anyway.

@wconstab
Copy link
Contributor Author

wconstab commented Apr 5, 2022

@wconstab has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

- default to generating forced fallback for TS backend (where it is used
for tests/debugging, but false otherwise

Differential Revision: [D35411211](https://our.internmc.facebook.com/intern/diff/D35411211)

[ghstack-poisoned]
@wconstab
Copy link
Contributor Author

wconstab commented Apr 5, 2022

@wconstab has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

- default to generating forced fallback for TS backend (where it is used
for tests/debugging, but false otherwise

Differential Revision: [D35411211](https://our.internmc.facebook.com/intern/diff/D35411211)

[ghstack-poisoned]
wconstab added a commit that referenced this pull request Apr 5, 2022
- default to generating forced fallback for TS backend (where it is used
for tests/debugging, but false otherwise

ghstack-source-id: 6fc42df
Pull Request resolved: #75274
@wconstab
Copy link
Contributor Author

wconstab commented Apr 5, 2022

@wconstab has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

facebook-github-bot pushed a commit that referenced this pull request Apr 6, 2022
Summary:
Pull Request resolved: #75274

- default to generating forced fallback for TS backend (where it is used
for tests/debugging, but false otherwise

Test Plan: Imported from OSS

Reviewed By: bdhirsh

Differential Revision: D35411211

Pulled By: wconstab

fbshipit-source-id: ccff2f65aa5d8e1aa670d210ce51805985df55ce
@github-actions
Copy link
Contributor

github-actions bot commented Apr 6, 2022

Hey @wconstab.
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.

@wconstab wconstab added topic: not user facing topic category release notes: lazy release notes category labels Apr 6, 2022
@facebook-github-bot facebook-github-bot deleted the gh/wconstab/3/head branch April 9, 2022 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants