Nvfuser code base nuke

[jjsjann123]

removing nvfuser code base.

cc @albanD

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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

✅ No Failures

As of commit 34e2881 with merge base 2f09da3 ():
💚 Looks good so far! There are no failures yet. 💚

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

[jjsjann123]

I don't think failing tests are relevant. I'm gonna wait until viable/strict catches up to retry CI. 😆

[jjsjann123]

This is breaking the 2k LOC sanity check.

But it's just removing dead code. Can we make an exception on that here, otherwise, it's going to be a ~85 PRs. 😆 cc'ing @malfet

Meanwhile, since I'm removing some bazel build files, would you mind try import and run this? @davidberard98

[facebook-github-bot]

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

[malfet]

@jjsjann123 i'm fine with ignoring this check (also, let me modify it to never fire up if total is net negative)

[facebook-github-bot]

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

[albanD]

Yes completely fine to skip this!

[davidberard98]

@pytorchbot rebase

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Rebase failed due to Command git -C /home/runner/work/pytorch/pytorch rebase refs/remotes/origin/viable/strict pull/111447/head returned non-zero exit code 1

Rebasing (1/2)
CONFLICT (modify/delete): third_party/nvfuser/test/test_gpu3.cpp deleted in ad57aef02ba (removing nvfuser code base) and modified in HEAD.  Version HEAD of third_party/nvfuser/test/test_gpu3.cpp left in tree.
error: could not apply ad57aef02ba... removing nvfuser code base
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply ad57aef02ba... removing nvfuser code base

Raised by https://github.com/pytorch/pytorch/actions/runs/6662910163

[davidberard98]

@jjsjann123 can you do the manual rebase please?

[jjsjann123]

merged viable/strict. Let me know if you want main instead.

[facebook-github-bot]

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

[davidberard98]

@pytorchbot rebase -s

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Rebase failed due to Command git -C /home/runner/work/pytorch/pytorch rebase refs/remotes/origin/viable/strict pull/111447/head returned non-zero exit code 1

Rebasing (1/2)
CONFLICT (modify/delete): third_party/nvfuser/test/test_gpu3.cpp deleted in ad57aef02ba (removing nvfuser code base) and modified in HEAD.  Version HEAD of third_party/nvfuser/test/test_gpu3.cpp left in tree.
error: could not apply ad57aef02ba... removing nvfuser code base
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply ad57aef02ba... removing nvfuser code base

Raised by https://github.com/pytorch/pytorch/actions/runs/6706601765

[albanD]

@davidberard98 if this is too prone to merge conflicts, it might be simpler to rebase + insta merge yourself.
The merge conflicts should be pretty clear.

[jjsjann123]

Let me do manual rebase.

[jjsjann123]

merged upstream/viable/strict cc'ing @davidberard98

[davidberard98]

thanks!

(btw, I'm kind of confused why the automated rebase didn't work; test_gpu3.cpp doesn't seem like it has changed since your last manual merge?)

[facebook-github-bot]

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

[jjsjann123]

thanks!

(btw, I'm kind of confused why the automated rebase didn't work; test_gpu3.cpp doesn't seem like it has changed since your last manual merge?)

Indeed!

There's no merge conflict when I just merged to upstream/viable/strict. But this isn't the first time with a false merge conflict from the bot.

[jjsjann123]

CI failure looks mysterious. The import did happen after my last rebase.

Meta Internal-Only Changes Check — The Diff and Pull Request are not in sync!

[facebook-github-bot]

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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