Skip to content

Conversation

@npmiller
Copy link
Contributor

I believe the issue was that the tests wasn't getting the CUDA target flags properly and this would have been fixed as part of the E2E tests rework (in #9336).

Fixes: #9174

@npmiller npmiller requested a review from a team as a code owner June 16, 2023 14:36
@npmiller npmiller temporarily deployed to aws June 16, 2023 14:43 — with GitHub Actions Inactive
@npmiller npmiller temporarily deployed to aws June 16, 2023 15:21 — with GitHub Actions Inactive
@abagusetty
Copy link
Contributor

Can this test be also enabled for HIP backend, as it seems to work on my end.

@npmiller
Copy link
Contributor Author

It seems this was already re-enabled for HIP now.

Friendly ping @sergey-semenov @intel/llvm-reviewers-runtime

I believe the issue was that the tests wasn't getting the CUDA target
flags properly and this would have been fixed as part of the E2E tests
rework.
@npmiller
Copy link
Contributor Author

ping @intel/llvm-reviewers-runtime @sergey-semenov @steffenlarsen

@sergey-semenov sergey-semenov merged commit 491fb26 into intel:sycl Sep 18, 2023
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.

Regression/same_unnamed_kernels.cpp failing in CUDA CI with PI_ERROR_INVALID_BINARY

3 participants