Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
build wheels without build isolation #1473
build wheels without build isolation #1473
Changes from all commits
b983143
9e2ceef
8c747f5
7cf37ee
4477b70
d6f05c6
d18c3f7
6c64e73
cbfaf85
9744bcf
8256e35
28e34eb
8251aaa
130e761
29b005e
fc8d575
ec06a4a
cb6b07d
75eaf12
7b87cd6
f59a067
1199e31
5e54225
9f979b5
aa62971
b4cd177
69fa9e8
8b841c2
e5d02b9
dd7a7a6
336bc27
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
sccache
stats printing for conda builds as well based on rapidsai/build-planning#111 and offline conversation with @vyasr .example build with these: https://github.com/rapidsai/cuspatial/actions/runs/11465788119/job/31906443973?pr=1473
Why not
build.sh
?Here, I'm proposing that these be put in
ci/build_{cpp,python}.sh
, wrapped around anyconda mambabuild
invocations that will end up compiling anything (so, for example, I included them inbuild_python.sh
becausecuspatial
andcuproj
both have some Cython extensions).I think this is preferable to
build.sh
, because thebuild_{cpp,python}.sh
scripts are unambiguously for CI, and can unconditionally invokesccache
.build.sh
is invoked in CI, but it's also intended for local use, and I didn't want to assume the presence ofsccache
for all local builds are introduce the complexity of having to check for its use.There are also some projects, like
cuvs
, that have their own handling of printingsccache
stats and creating build summary reports based on them inbuild.sh
, and I didn't want to interfere with that.example:
https://github.com/rapidsai/cuvs/blob/e7f1085b71c340b9600f5f38f7f0059a5c7aa806/build.sh#L364-L366
https://github.com/rapidsai/cuvs/blob/e7f1085b71c340b9600f5f38f7f0059a5c7aa806/build.sh#L408-L424