-
Notifications
You must be signed in to change notification settings - Fork 807
[SYCL][E2E][NATIVE_CPU] Add Native CPU e2e PR testing #19961
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][E2E][NATIVE_CPU] Add Native CPU e2e PR testing #19961
Conversation
bb77a72
to
991d38e
Compare
7a79656
to
918523a
Compare
918523a
to
3ea3d02
Compare
3ea3d02
to
95496d2
Compare
95496d2
to
2756583
Compare
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.
LGTM
@intel/dpcpp-sanitizers-review @intel/dpcpp-esimd-reviewers @intel/unified-runtime-reviewers-level-zero @intel/unified-runtime-reviewers I am running out of time for this to be reviewed. |
@intel/dpcpp-sanitizers-review @intel/dpcpp-esimd-reviewers if you have the spare capacity tomorrow (Wed) to review it would be very much appreciated. |
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.
esimd lgtm
8950697
to
4466aef
Compare
The Native CPU work is being passed onto a team in Intel now that all of Native CPU is independent of the oneAPI Construction Kit. Native CPU does not pass all of E2E testing, either through bugs or unimplemented functionality. All are currently being marked as UNSUPPORTED until these failures are processed and tracked by the new team. This also adds a separate job for E2E build and run for Native CPU, as it cannot be added to the prebuilt due to build fails.
4466aef
to
cf794bd
Compare
@intel/llvm-gatekeepers Is it possible to merge this, I've got 4 approvals and the only reason for the sanitizer one is to add some UNSUPPORTED across the sanitizers. There is increasingly limited time and there is a dependent PR. |
Reran it again and it turned green. Probably just infrastructural. I am going to make the executive decision to merge this. @intel/dpcpp-sanitizers-review - Feel free to do a post-commit review and we can address them in a follow-up. |
The Native CPU work is being passed onto a team in Intel now that
all of Native CPU is independent of the oneAPI Construction Kit.
Native CPU does not pass all of E2E testing, either through bugs or
unimplemented functionality. Most are currently being marked as
UNSUPPORTED until these failures are processed and tracked by the new
team, with a smaller number marked as XFAIL. These are being tracked under #20142.
This also adds a separate job for E2E build and run for Native CPU,
as it cannot be added to the prebuilt due to build fails.