-
Notifications
You must be signed in to change notification settings - Fork 49
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
Fix GPGPU provider distribution (New) #1542
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1542 +/- ##
===========================================
+ Coverage 48.00% 91.13% +43.12%
===========================================
Files 371 3 -368
Lines 39837 327 -39510
Branches 6733 38 -6695
===========================================
- Hits 19125 298 -18827
+ Misses 19994 28 -19966
+ Partials 718 1 -717
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Ok, the next step should be to get the repository setup part of the |
I'm wondering if the compiling should actually be part of |
19c5320
to
aa87cdc
Compare
These files are created by the system being tested. They shouldn't be pushed to github.
Now gpu-setup is merely installing dependencies for the provider. Ideally, these dependencies will get pulled in by the snap or deb package, and the system will be able to compile the tests. TOOD: With AMD tests being added, this Makefile will need to be skipped if the system being used does not have NVIDIA GPUs.
I'm curious to see if the packaging will succeed with what we have in the Ubuntu repositories. I'm skeptical, though.
The projects are downloaded to `/opt/` but the binaries are symlinked to `/usr/local/sbin`. Need to test if the symlinks are able to find the necessary data files.
The preinst and postinst solution did not work. preinst does not run before the dependency handling occurs.
This should be installed already, but might as well
These are no longer going to be living inside the data directory
44f8e49
to
d308544
Compare
Description
Currently, the GPGPU provider depends on the user running a setup script after installing the provider. This script sets up the NVIDIA/AMD repositories to get the required packages from upstream (i.e. CUDA toolkit or ROCm). This has worked so far, but it is negatively affecting the way we test the provider, especially with automated setups.
Resolved issues
Resolves CHECKBOX-1519
Documentation
Tests