This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Fix Windows GPU CI #17962
Merged
Merged
Fix Windows GPU CI #17962
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Submodule dmlc-core
updated
19 files
+38 −0 | .github/workflows/githubci.yml | |
+0 −87 | .travis.yml | |
+1 −1 | README.md | |
+13 −0 | appveyor.yml | |
+0 −1 | cmake/build_config.h.in | |
+1 −16 | doc/Doxyfile | |
+0 −1 | include/dmlc/build_config_default.h | |
+18 −18 | include/dmlc/concurrentqueue.h | |
+7 −14 | scripts/packages.mk | |
+0 −0 | scripts/s390x/Dockerfile | |
+0 −0 | scripts/s390x/build_via_cmake.sh | |
+1 −1 | scripts/s390x/ci_build.sh | |
+0 −0 | scripts/s390x/entrypoint.sh | |
+0 −32 | scripts/setup_nvcc.sh | |
+9 −5 | scripts/test_script.sh | |
+0 −3 | scripts/travis/travis_before_cache.sh | |
+0 −13 | scripts/travis/travis_osx_install.sh | |
+0 −40 | scripts/travis/travis_setup_env.sh | |
+0 −16 | src/build_config.cc |
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
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.
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.
Please revert the CUDA change. That does not represent a fix.
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.
It's a requirement for VS2019
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.
Usually visual studio does allow more than one cuda version. You just have to install the respective Toolkit.
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.
What do you mean? Cuda 9.2 does not support VS 2019
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.
You can read for example https://superuser.com/questions/1506044/installing-cuda-9-2-with-vs-2019 or https://devblogs.microsoft.com/cppblog/cuda-10-1-available-now-with-support-for-latest-microsoft-visual-studio-2019-versions/
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.
Oh, they intentionally broke that backwards compatibility feature. Usually it was possible to compile older cuda versions in later vs versions by installing toolkits which make sure that the integration is available. Seems like that caused issues and thus Microsoft and Nvidia decided to not go that route any further.
In that case, find to proceed.
But is there still some kind of compatibility mode which checks that the is still compliant with older cuda standards?
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.
No. Unix & CentOS tests Cuda 10.1. Windows now tests Cuda 10.2.
But the risk is low that we'd break Cuda 9 support within the next few days. So it's not a one-way door decision. I suggest we discuss on dev if we want to support cuda 9. If we decide to support it, let's switch the CentOS tests to use Cuda 9.