Skip to content

remove fast_flush arguments#135387

Closed
int3 wants to merge 3 commits intogh/int3/102/basefrom
gh/int3/102/head
Closed

remove fast_flush arguments#135387
int3 wants to merge 3 commits intogh/int3/102/basefrom
gh/int3/102/head

Conversation

@int3
Copy link
Contributor

@int3 int3 commented Sep 6, 2024

Stack from ghstack (oldest at bottom):

I've removed them from upstream Triton in triton-lang/triton#4485. It looks like most places in the code use the default value of fast_flush=True anyway, though there are two PRs from @pearu that use False. To my knowledge, there's no reason to use the False value.

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang

Differential Revision: D62325778

[ghstack-poisoned]
int3 added a commit that referenced this pull request Sep 6, 2024
ghstack-source-id: d837b9b
Pull Request resolved: #135387
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 6, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/135387

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (3 Unrelated Failures)

As of commit 90264ca with merge base 3e1a4ea (image):

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@int3
Copy link
Contributor Author

int3 commented Sep 6, 2024

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

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Sep 10, 2024
I've removed them from upstream Triton in triton-lang/triton#4485. It looks like most places in the code use the default value of `fast_flush=True` anyway, though there are two PRs from pearu that use `False`. To my knowledge, there's no reason to use the `False` value.

cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy yf225 chenyang78 kadeng muchulee8 ColinPeppler amjames desertfire chauhang

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

[ghstack-poisoned]
int3 added a commit that referenced this pull request Sep 11, 2024
ghstack-source-id: 2f506f0
Pull Request resolved: #135387
@int3 int3 added the topic: not user facing topic category label Sep 11, 2024
@int3
Copy link
Contributor Author

int3 commented Sep 11, 2024

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: This PR has internal changes and must be landed via Phabricator! Please try reimporting/rexporting the PR!

Details for Dev Infra team Raised by workflow job

I've removed them from upstream Triton in triton-lang/triton#4485. It looks like most places in the code use the default value of `fast_flush=True` anyway, though there are two PRs from pearu that use `False`. To my knowledge, there's no reason to use the `False` value.

cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy yf225 chenyang78 kadeng muchulee8 ColinPeppler amjames desertfire chauhang

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

[ghstack-poisoned]
int3 added a commit that referenced this pull request Sep 13, 2024
ghstack-source-id: e105e67
Pull Request resolved: #135387
@facebook-github-bot
Copy link
Contributor

@pytorchbot merge -f 'Landed internally'

(Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally)

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Chao1Han pushed a commit to Chao1Han/pytorch that referenced this pull request Sep 20, 2024
I've removed them from upstream Triton in triton-lang/triton#4485. It looks like most places in the code use the default value of `fast_flush=True` anyway, though there are two PRs from @pearu that use `False`. To my knowledge, there's no reason to use the `False` value.

Differential Revision: [D62325778](https://our.internmc.facebook.com/intern/diff/D62325778)
Pull Request resolved: pytorch#135387
Approved by: https://github.com/nmacchioni, https://github.com/jansel
anmyachev added a commit to intel/intel-xpu-backend-for-triton that referenced this pull request Sep 29, 2024
@github-actions github-actions bot deleted the gh/int3/102/head branch October 14, 2024 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request Merged module: inductor release notes: sparse release notes category topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants