The artifact’s main executable is self-documenting using the -h or –help CLI option. The specific steps are documented in the top-level README file in the GitHub repository. This option requires a physical or virtual Debian-based system on Intel hardware, which may include an accelerator, such as a GPU. To observe execution in real time or after completion, one can drill into this entry until the step-by-step execution log appears. This will create an entry under the GitHub actions tab for this workflow run. Use the web interface to create a file, say “dummy.txt”, to trigger a workflow run. Visit the Actions tab, where you will see the message “Workflows aren’t being run on this forked repository.”Ĭlick on the green button labeled “I understand my workflows, go ahead and enable them.” Near the top right corner, look for the Fork button, click on the dropdown, and select “Create a new fork.”Ĭreate the new fork in your GitHub account or organization. Visit /LoyolaChicagoCode/unoapi-dpcpp-examples. These are the steps to copy, build, and run the artifact in a web browser without involving a local build environment. This option is subject to limitations in devices available through the actual CI container (i.e., not usually accelerators). 6 7wget -qO- \ 8 \ 9GPG-PUB-KEY-INTEL-SW-PRODUCTS.PUB | \ 10 sudo tee /etc/apt// \ 11GPG-PUB-KEY-INTEL-SW-PRODUCTS.ascġ2 echo "deb " \ 13 "all main" | \ 14 sudo tee /etc/apt//oneAPI.listġ8 19sudo apt install intel-oneapi-compiler-dpcpp-cppĮvery commit or pull request to the repository triggers a build and results in an indication of successful or unsuccessful completion of the build, including execution of the unit test suite.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |