Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix CUPTI lookup to include target directory #148668

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix CUPTI lookup to include target directory #148668

wants to merge 1 commit into from

Conversation

mgorny
Copy link
Contributor

@mgorny mgorny commented Mar 6, 2025

CUPTI library and headers are installed to the target subdirectory rather than the top-level prefix in conda-forge. Include CUDAToolkit_TARGET_DIR subdirectories in CUPTI search paths to fix finding it in that environment.

@mgorny
Fix CUPTI lookup to include target directory
b0fbff5 
CUPTI library and headers are installed to the target subdirectory
rather than the top-level prefix in conda-forge.  Include
`CUDAToolkit_TARGET_DIR` subdirectories in CUPTI search paths to fix
finding it in that environment.
@pytorch-bot PyTorch Bot
Copy link

pytorch-bot bot commented Mar 6, 2025 •
edited
Loading

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit b0fbff5 with merge base d518490 (image):

NEW FAILURE - The following job has failed:

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

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Mar 6, 2025

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@mgorny mgorny mentioned this pull request Mar 6, 2025
Closed
1 task
@colesbury colesbury requested a review from malfet March 6, 2025 18:33
@colesbury colesbury added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Mar 6, 2025
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented May 5, 2025

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the Stale label May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@malfet malfet Awaiting requested review from malfet

Assignees
No one assigned
Labels
open source Stale triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@mgorny @colesbury @pytorchbot