[SYCL-MLIR][CI] Trigger SYCL MLIR Pre Commit on Linux workflow

[victor-eds]

Rename the workflow file so that our own SYCL MLIR Pre Commit on Linux is triggered instead of SYCL Pre Commit on Linux.

The latter lead to an additional job testing SYCL-MLIR on CUDA devices (always failing).

Note: Future changes in sycl branch CI may lead to conflicts when merging.

[victor-eds]

@bader you were totally right. I checked what was going on and, apparently, despite naming a different workflow in the .yml file, the SYCL Pre Commit on Linux was being triggered. This change triggers our own workflow, so no additional jobs like the CUDA AWS one will be triggered.

[whitneywhtsang]

The latter lead to an additional job testing SYCL-MLIR on CUDA devices (always failing).

Why .github/workflows/sycl_precommit_linux.yml would trigger CUDA testing? Where is that define?

[victor-eds]

Why .github/workflows/sycl_precommit_linux.yml would trigger CUDA testing? Where is that define?

Nowhere to be found. I'm no CI expert, but, looking at previous jobs, it seems our workflow was being run with a different name (?).

[jsji]

The latter lead to an additional job testing SYCL-MLIR on CUDA devices (always failing).

Why .github/workflows/sycl_precommit_linux.yml would trigger CUDA testing? Where is that define?

My understanding is: https://github.com/intel/llvm/blob/sycl/.github/workflows/sycl_precommit_aws.yml use

workflow_run:
workflows: [SYCL Pre Commit on Linux]

So as long as the workflow name pre commit testing is SYCL Pre Commit on Linux, it will trigger the CUDA testing in sycl_precommit_aws.yml.

And according to https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows

Note: This event will only trigger a workflow run if the workflow file is on the default branch.

So changing the workflow name in sycl_precommit_aws.yml in SYCL-MLIR branch won't help, as it is not on the default branch.

So yeah, it is good idea to rename the workflow for SYCL-MLIR branch to something else other than SYCL Pre Commit on Linux.

[victor-eds]

So yeah, it is good idea to rename the workflow for SYCL-MLIR branch to something else other than SYCL Pre Commit on Linux.

We already had:

name: SYCL MLIR Pre Commit on Linux

but our workflow appeared with the SYCL Pre Commit on Linux name when looked in this project's actions (not in CI report in the PRs, tho). My crazy bet is that the name was taken from the sycl branch file due to the filename collision.

[whitneywhtsang]

our workflow appeared with the SYCL Pre Commit on Linux name when looked in this project's actions

Where do you see that?
https://github.com/intel/llvm/actions/runs/5962217402/workflow?pr=10952 also appeared as SYCL MLIR Pre Commit on Linux.

[victor-eds]

our workflow appeared with the SYCL Pre Commit on Linux name when looked in this project's actions

Where do you see that? https://github.com/intel/llvm/actions/runs/5962217402/workflow?pr=10952 also appeared as SYCL MLIR Pre Commit on Linux.

Here you can see jobs triggered by PRs both targeting sycl and sycl-mlir, and here, just the job triggered by this PR making the change. If this is intended GitHub behavior, it's a bit obscure for the untrained eye, TBH.

[aelovikov-intel]

our workflow appeared with the SYCL Pre Commit on Linux name when looked in this project's actions

Where do you see that? https://github.com/intel/llvm/actions/runs/5962217402/workflow?pr=10952 also appeared as SYCL MLIR Pre Commit on Linux.

Here you can see jobs triggered by PRs both targeting sycl and sycl-mlir, and here, just the job triggered by this PR making the change. If this is intended GitHub behavior, it's a bit obscure for the untrained eye, TBH.

I can't tell enough how I hate Github Actions after working with them very closely for the last half a year. Everything looks cumbersome, unfinished and buggy. The developers seem to jump from one thing to another without polishing anything for the release quality...

[victor-eds]

I can't tell enough how I hate Github Actions after working with them very closely for the last half a year. Everything looks cumbersome, unfinished and buggy. The developers seem to jump from one thing to another without polishing anything for the release quality...

This looks definitely like a bug to me (maybe they'll document it and make it a feature now 😆). Thanks for the reviews guys, CI can be painful.