-
Notifications
You must be signed in to change notification settings - Fork 26.3k
properly skip legacy tests regardless of the default executor #40381
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
Conversation
💊 CI failures summary and remediationsAs of commit f8e3368 (more details on the Dr. CI page):
🕵️ 1 new failure recognized by patternsThe following CI failures do not appear to be due to upstream breakages:
|
facebook-github-bot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Krovatkin has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
|
@Krovatkin merged this pull request in 5036c94. |
…h#40381) Summary: Pull Request resolved: pytorch#40381 Differential Revision: D22173938 Pulled By: Krovatkin fbshipit-source-id: 305fc4484977e828cc4cee6e053a1e1ab9f0d6c7
…h#40381) Summary: Pull Request resolved: pytorch#40381 Differential Revision: D22173938 Pulled By: Krovatkin fbshipit-source-id: 305fc4484977e828cc4cee6e053a1e1ab9f0d6c7
* properly skip legacy tests regardless of the default executor (#40381) Summary: Pull Request resolved: #40381 Differential Revision: D22173938 Pulled By: Krovatkin fbshipit-source-id: 305fc4484977e828cc4cee6e053a1e1ab9f0d6c7 * [JIT] Switch executor from Simple to Legacy. This is done for 1.6 only in order to recover performance regressions caused by the Legacy->Simple switch that was done in 1.5. On master we still plan to use Simple executor and fix the performance issues in 1.7 without falling back to the Legacy executor. Co-authored-by: Nikolay Korovaiko <[email protected]>
No description provided.