Skip to content
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

[CI] New workflow for SYCL-CTS with SPIR-V backend #16731

Merged
merged 3 commits into from
Jan 24, 2025
Merged

[CI] New workflow for SYCL-CTS with SPIR-V backend #16731

merged 3 commits into from
Jan 24, 2025

Conversation

KornevNikita
Copy link
Contributor

This patch adds new workflow to build SYCL-CTS with SPIR-V backend and run it on gen12 OCL CPU and PVC L0 GPU. It will be launched only on Sundays.

This patch adds new workflow to build SYCL-CTS with SPIR-V backend and
run it on gen12 OCL CPU and PVC L0 GPU. It will be launched only on
Sundays.
@KornevNikita KornevNikita requested a review from a team as a code owner January 22, 2025 13:03
@KornevNikita
Copy link
Contributor Author

@VyacheslavLevytskyy FYI

@VyacheslavLevytskyy
Copy link
Contributor

CC: @sarnex @aelovikov-intel FYI

.github/workflows/sycl-cts-on-spirv-be.yml Outdated Show resolved Hide resolved
.github/workflows/sycl-cts-on-spirv-be.yml Outdated Show resolved Hide resolved
.github/workflows/sycl-cts-on-spirv-be.yml Outdated Show resolved Hide resolved
.github/workflows/sycl-cts-on-spirv-be.yml Outdated Show resolved Hide resolved
.github/workflows/sycl-cts-on-spirv-be.yml Outdated Show resolved Hide resolved
@KornevNikita
Copy link
Contributor Author

@aelovikov-intel @uditagarwal97 hi! Any comments there or this can be merged?

@aelovikov-intel
Copy link
Contributor

@aelovikov-intel @uditagarwal97 hi! Any comments there or this can be merged?

I'd rename to sycl-weekly.yml as that is the reason we keep CTS+SPIRV backend separate from other testing. That said, as long as it's a new file, Nick's approval is enough for me to not even look into this :)

@sarnex
Copy link
Contributor

sarnex commented Jan 24, 2025

That said, as long as it's a new file, Nick's approval is enough for me to not even look into this :)

😟

image_options: -u 1001 --device=/dev/dri --privileged --cap-add SYS_ADMIN
tests_selector: cts
ref: ${{ github.sha }}
sycl_toolchain_artifact: sycl_linux_default
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to set merge_ref to empty anywhere in this workflow?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, it's only needed for build

Copy link
Contributor

@uditagarwal97 uditagarwal97 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@sarnex
Copy link
Contributor

sarnex commented Jan 24, 2025

just renamed file, dont need to run ci again

@sarnex sarnex merged commit 4d3d4e6 into sycl Jan 24, 2025
3 of 6 checks passed
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.

5 participants