Skip to content

Add USE_SYSTEM_NVTX option #138287

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

Closed
wants to merge 1 commit into from

Conversation

jeongseok-meta
Copy link
Contributor

@jeongseok-meta jeongseok-meta commented Oct 18, 2024

Summary

We are currently updating the conda-forge::pytorch package to version 2.5.0. This update includes a new dependency, the third_party/NVTX submodule. However, like other package management frameworks (e.g., apt), conda-forge prefers using system-installed packages instead of vendor-provided third-party packages.

This pull request aims to add an option, USE_SYSTEM_NVTX, to select whether to use the vendored nvtx or the system-installed one, with the default being the vendored one (which is the current behavior).

Test Plan

The USE_SYSTEM_NVTX option is tested by building the conda-forge::pytorch package with the change applied as a patch.

Copy link

linux-foundation-easycla bot commented Oct 18, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: jeongseok-meta / name: Jeongseok (JS) Lee (3b8cc1c)

Copy link

pytorch-bot bot commented Oct 18, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit 3b8cc1c with merge base e8b1409 (image):
💚 Looks good so far! There are no failures yet. 💚

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

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Oct 18, 2024
@jeongseok-meta
Copy link
Contributor Author

Please remove the topic: not user facing tag as it was accidentally added.

@facebook-github-bot
Copy link
Contributor

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

@jeongseok-meta
Copy link
Contributor Author

@pytorchbot label "release notes: build"

@pytorch-bot pytorch-bot bot added the release notes: build release notes category label Oct 18, 2024
@jeongseok-meta jeongseok-meta marked this pull request as ready for review October 18, 2024 00:24
Copy link
Collaborator

@albanD albanD left a comment

Choose a reason for hiding this comment

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

Sounds good!
Thanks for update the comment in setup.py to be accurate!

@cyyever
Copy link
Collaborator

cyyever commented Oct 18, 2024

USE_SYSTEM_NVTX defaults to true? It's better to use the NVTX associated with CUDA.

@albanD
Copy link
Collaborator

albanD commented Oct 18, 2024

It default to the same value as "USE_SYSTEM_LIBS" (which is off by default).

@jeongseok-meta
Copy link
Contributor Author

@cyyever It is defaulted to OFF to maintain the current behavior (and it can be overwritten by USE_SYSTEM_LIBS like any other USE_SYSTEM_* options). We could change the behavior in a follow-up PR if needed, in my opinion.

@jeongseok-meta
Copy link
Contributor Author

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 18, 2024
@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: Auto Request Review

Details for Dev Infra team Raised by workflow job

@albanD
Copy link
Collaborator

albanD commented Oct 18, 2024

@pytorchbot merge -r

Not sure why this job failed...

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Successfully rebased use_system_nvtx onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout use_system_nvtx && git pull --rebase)

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 2 jobs have failed, first few of them are: linux-binary-manywheel / manywheel-py3_9-cuda12_4-build / build, linux-binary-manywheel / manywheel-py3_9-cuda11_8-build / build

Details for Dev Infra team Raised by workflow job

@jeongseok-meta
Copy link
Contributor Author

@pytorchbot merge -r

Copy link

pytorch-bot bot commented Oct 18, 2024

You don't have permissions to rebase this PR since you are a first time contributor. If you think this is a mistake, please contact PyTorch Dev Infra.

@pytorchmergebot
Copy link
Collaborator

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

@jeongseok-meta
Copy link
Contributor Author

@pytorchbot rebase

Copy link

pytorch-bot bot commented Oct 18, 2024

You don't have permissions to rebase this PR since you are a first time contributor. If you think this is a mistake, please contact PyTorch Dev Infra.

@jeongseok-meta
Copy link
Contributor Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 3 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@jeongseok-meta
Copy link
Contributor Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request Merged release notes: build release notes category topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants