-
Notifications
You must be signed in to change notification settings - Fork 738
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
[SYCL][NATIVECPU][CI] Enable Native CPU without OCK on linux build #13052
[SYCL][NATIVECPU][CI] Enable Native CPU without OCK on linux build #13052
Conversation
Hi @intel/dpcpp-devops-reviewers, the main job affected by this PR ( |
This change also triggered post-commit task and |
Should we do |
Yeah you are right, but I see |
Probably. The main difference in pre- vs post- is that in pre-commit end-to-end tests we use multiple SYCL devices in a single invocation that results in XFAIL-marked tests to be simply skipped. Post-commit uses one SYCL device per |
The error in the post commit linux build pipeline is due to the fact that we run some SYCL executables in the tests in |
@intel/dpcpp-devops-reviewers I've undrafted this PR since the Post Commit Linux Build job executed successfully (in the log you can see that the build was configured with |
Hi @aelovikov-intel, coming back to this PR, the pre-commit failure on CUDA is seen in other PRs e.g. #13695. The failure on the Arc job seems to appear also in this run, associated to commit |
This PR enables the Native CPU plugin in the build jobs for Linux. It is the first PR in series, with the goal of enabling full
e2e
testing for the Native CPU plugin on both Linux and Windows.This initial PR builds the Native CPU plugin without the oneAPI Construction Kit. While the oneAPI Construction Kit is currently a key component for Native CPU, I would prefer to keep things as simple as possible, and enable CI testing for additional features incrementally, in order to gradually assess the impact of the Native CPU plugin in the overall CI workflow.