Skip to content

Explicitly state which extension uses cpp files #361

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

Merged
merged 1 commit into from
Jan 8, 2025

Conversation

vzhurba01
Copy link
Collaborator

@vzhurba01 vzhurba01 commented Jan 7, 2025

Since each cpp is only used by a single extension, a simple solution is to expand the regex pattern and specify which extension uses it directly. Both private and utils have limited number of pyx files and therefore this regex expansion doesn't bloat either.

close #271

@vzhurba01 vzhurba01 self-assigned this Jan 7, 2025
Copy link
Contributor

copy-pr-bot bot commented Jan 7, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@vzhurba01
Copy link
Collaborator Author

/ok to test

@vzhurba01 vzhurba01 changed the title Draft: Explicitly state which exntension uses cpp files Explicitly state which exntension uses cpp files Jan 7, 2025
@vzhurba01 vzhurba01 requested a review from leofang January 7, 2025 20:32
@vzhurba01 vzhurba01 changed the title Explicitly state which exntension uses cpp files Explicitly state which extension uses cpp files Jan 7, 2025
Each cpp file is only used by a single extension
@vzhurba01 vzhurba01 force-pushed the resolve-parallel-builds branch from 5370db7 to 8620a28 Compare January 7, 2025 20:47
@vzhurba01
Copy link
Collaborator Author

/ok to test

@leofang
Copy link
Member

leofang commented Jan 8, 2025

Let me rerun the CI one more time and see if we could still trigger the flaky builds.

@leofang leofang closed this Jan 8, 2025
@leofang leofang reopened this Jan 8, 2025
@leofang
Copy link
Member

leofang commented Jan 8, 2025

/ok to test

@leofang leofang added bug Something isn't working P0 High priority - Must do! cuda.bindings Everything related to the cuda.bindings module to-be-backported Trigger the bot to raise a backport PR upon merge labels Jan 8, 2025
@leofang leofang added this to the cuda-python 12-next, 11-next milestone Jan 8, 2025
@leofang
Copy link
Member

leofang commented Jan 8, 2025

Seems like it works. Let's merge and keep an eye on it. Thanks, Vlad!

@vzhurba01
Copy link
Collaborator Author

Looks like all builds passed. Merging. Thanks!

@leofang leofang merged commit e774b32 into NVIDIA:main Jan 8, 2025
99 checks passed
Copy link

github-actions bot commented Jan 8, 2025

Successfully created backport PR for 11.8.x:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cuda.bindings Everything related to the cuda.bindings module P0 High priority - Must do! to-be-backported Trigger the bot to raise a backport PR upon merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Building cuda.bindings in parallel might fail non-deterministically
2 participants