-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Add other Linux GPU auxiliary test jobs #61055
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 a15e5e8 (more details on the Dr. CI page and at hud.pytorch.org/pr/61055): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 Preview docs built from this PR 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. |
|
@samestep has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
|
question for reviewers: any idea why the |
| test_runner_type: str, | ||
| on_pull_request: bool = False, | ||
| enable_doc_jobs: bool = False, | ||
| enable_jit_legacy_test: YamlShellBool = "''", |
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.
What is the advantage of using YamlShellBool with '' and 1s instead of just having Trues/Falses with bools? Is it for better compat between shell and script?
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.
Is it for better compat between shell and script?
Yeah exactly; this variable gets set as an environment variable, so it's easier for both shell and Python scripts to consume it if false is represented as the empty string.
walterddr
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.
looks good!
| IN_PULL_REQUEST=${CIRCLE_PULL_REQUEST:-} | ||
|
|
||
| if [[ "$BUILD_ENVIRONMENT" == *-slow-* ]]; then | ||
| if [[ "$BUILD_ENVIRONMENT" == *-slow-* || $TEST_CONFIG == 'slow' ]]; then |
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.
shellscript noob q:
what's the difference between double quoted variable "$BLA", bracketed "${BLA}" and naked $BLA here?
i am sensing it might be relate to macos/linux convention but i dunno why there's so much inconsistent in these if statementss
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.
there's no difference between using quotes vs not within [[ double brackets ]], which is why shellcheck doesn't complain here; also the curly braces are basically never necessary, so idk why people are using them in general here
|
@samestep has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
jit_legacynogpu_NO_AVXnogpu_NO_AVX2slowTest plan:
CI. Example run: https://github.com/pytorch/pytorch/actions/runs/1013240987