Skip to content

[SYCL][E2E] Mark a test as unsupported on accelerator #10037

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

Merged

Conversation

cperkinsintel
Copy link
Contributor

@cperkinsintel cperkinsintel commented Jun 22, 2023

This test used to be only run on the CPU and GPU but when we moved to the %{run} notation, it wasn't marked as unsupported on accelerator. It seems unsupported on accelerator. The clCreateProgramWithIL() call is returning and error -59 when the accelerator device is the one behind the context. I went back and checked and it has never worked on accelerator. I'll make a note in the online compiler tickets and if this is a real error, a ticket will be opened. But the test should be restored so to not be run on accelerator.

… the %{run} notation, it wasn't marked as unsupported on accelerator. It seems unsupported on accelerator. The clCreateProgramWithIL() call is returning and error -59 when the accelerator device is the one behind the context. I went back and checked and it has never worked on accelerator.
@cperkinsintel cperkinsintel requested a review from a team as a code owner June 22, 2023 23:45
@cperkinsintel cperkinsintel temporarily deployed to aws June 22, 2023 23:45 — with GitHub Actions Inactive
@cperkinsintel cperkinsintel temporarily deployed to aws June 23, 2023 00:18 — with GitHub Actions Inactive
@cperkinsintel
Copy link
Contributor Author

The test failures are unrelated. Note that this particular test is needlessly failing on accelerator on other PRs, so it'd be nice to get this one approved/merged to help others.

@aelovikov-intel aelovikov-intel changed the title [SYCL] test update - should be marked unsupported on accelerator [SYCL][E2E] Mark a test as unsupported on accelerator Jun 28, 2023
@aelovikov-intel
Copy link
Contributor

Failures are unrelated - happen on e2e tests that aren't modified here. I have in-progress #10100 to address most of them (hopefully).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants