Skip to content

Conversation

@ianayl
Copy link
Contributor

@ianayl ianayl commented Oct 9, 2025

This PR adds precompiled CTS binaries to sycl-prebuilt-e2e-container.yml.

Note that this PR also renames some fields in devops/actions/run-tests/cts/action.yml to match that of run-tests/e2e/action.yml. If this is unwanted I will undo the changes.

@ianayl ianayl requested a review from a team as a code owner October 9, 2025 19:43
@sarnex sarnex requested a review from aelovikov-intel October 9, 2025 19:45
@ianayl
Copy link
Contributor Author

ianayl commented Oct 9, 2025

@aelovikov-intel ping for awareness

@ianayl
Copy link
Contributor Author

ianayl commented Oct 9, 2025

Test run at https://github.com/intel/llvm/actions/runs/18386413684

CTS tests are running as expected, but there seems to be a single failure. It doesn't seem to be related to the workflow, but I still need to look into why it is failing.

@KornevNikita
Copy link
Contributor

Let's also update the description in sycl-prebuilt-e2e-container.yml:

# The purpose of this is to build E2E tests with the latest release toolchain
# and then run them with the trunk SYCL RT (libsycl.so and friends) to verify
# that ABI compatibility hasn't been broken.

Comment on lines +96 to +100
if: |
inputs.cts_testing_mode == 'run-only'
&& !(inputs.sycl_cts_artifact == 'in-container'
|| inputs.sycl_cts_artifact == ''
|| github.event_name == 'workflow_dispatch')
Copy link
Contributor

Choose a reason for hiding this comment

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

This is actually broken in run-tests/e2e/action.yml (I found out today), but I don't have a fix yet. In a nutshell, github_event_name corresponds to the top-level workflow (i.e., pull_request/workflow_dispatch/push) and not to how the sycl-linux-run-tests.yml has been invoked (dispatch vs call).

Copy link
Contributor

Choose a reason for hiding this comment

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

#20580 fixes it in trunk, this PR will need to be updated.

@aelovikov-intel
Copy link
Contributor

aelovikov-intel commented Oct 31, 2025

Manual run: https://github.com/intel/llvm/actions/runs/18959457462/job/54145504511

All CTS tests seem to be seg. faulting.

@ianayl
Copy link
Contributor Author

ianayl commented Oct 31, 2025

@aelovikov-intel That run seems to be using the main branch in intel/llvmI misread, you seemed to have used a hash; Do you happen to know what version the commit hash is from?

On HEAD in sycl, both main and hardcoded commit from sycl-rel-6_3 works:
Manual run using SYCL-CTS main: https://github.com/intel/llvm/actions/runs/18963497340
Manual run using hardcoded hash from sycl-rel-6_3: https://github.com/intel/llvm/actions/runs/18962672688

@aelovikov-intel
Copy link
Contributor

@aelovikov-intel That run seems to be using the main branch in intel/llvmI misread, you seemed to have used a hash; Do you happen to know what version the commit hash is from?

On HEAD in sycl, both main and hardcoded commit from sycl-rel-6_3 works: Manual run using SYCL-CTS main: https://github.com/intel/llvm/actions/runs/18963497340 Manual run using hardcoded hash from sycl-rel-6_3: https://github.com/intel/llvm/actions/runs/18962672688

Copying offline reply:

    cts_binaries_ref: 19e4ed34377c8a8a354d701772427be8c5430b0d
    cts_ref: 19e4ed34377c8a8a354d701772427be8c5430b0d
    ref: 4a905ca36143ffe0f4ef3a6b30cb366a76528ee1   # current sycl-rel-6_3

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