don't build for CUDA_ARCH 86 on 11.1 due to time outs #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
h-vetinari
force-pushed
the
unblock
branch
2 times, most recently
from
cbfd66a to
699a802
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After 10 CI (re-)runs of the merge commit from #32, win+cuda11.1 is the one build combination that - despite some fluctuation in lib build times between ~1:40 and 4:00 (which is necessary twice; for
libfaissandlibfaiss-avx2) - has not managed to have a successful run.This is to see if building for one less CUDA arch helps us get under the 6h limit (I have the suspicion from casual observation that 11.1 regressed in terms of compile times, but 11.2 is OK again).
As long as there's no successful build for win+cuda11.1, we also don't need to bump the build number here.