Skip to content

Conversation

lukaszstolarczuk
Copy link
Contributor

  • sycl-benchmark-aggregate.yml seems like a dead code
  • make benchmarks' README more up-to-date
  • fix some misspells found by codespell
  • add missing license in one of the scripts (is it the correct license?)

Copy link
Contributor

@sarnex sarnex left a comment

Choose a reason for hiding this comment

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

file delete lgtm, didnt check myself to see if its actually dead


To execute the benchmarks in CI, navigate to the `Actions` tab and then go to the `Compute Benchmarks` action. Here, you will find a list of previous runs and a "Run workflow" button. Upon clicking the button, you will be prompted to fill in a form to customize your benchmark run. The only mandatory field is the `PR number`, which is the identifier for the Pull Request against which you want the benchmarks to run.
To execute the benchmarks in CI, navigate to the `Actions` tab and then go to the `Run Benchmarks` workflow. Here, you will find a list of previous runs and a "Run workflow" button. Upon clicking the button, you will be prompted to fill in a form to customize your benchmark run. Important field is the `PR number`, which is the identifier for the Pull Request against which you want the benchmarks to run. Instead, you can specify `Commit hash` from within intel/llvm repository, or leave both
empty to run benchmarks against the latest commit from default branch.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think that the latest commit from the branch you pick up as the first drop-down list is taken in this case, but please verify that.

Copy link
Contributor

@ianayl ianayl Oct 15, 2025

Choose a reason for hiding this comment

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

Let me double check this, but IIRC that dropdown list version is: Pretty sure this is the case:

  • used if PR/commit hash is not provided
  • if PR/commit hash is provided, the dropdown list version only affects the version of benchmark workflow/suite used, the build still relies on PR/commit hash field

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@ianayl
Copy link
Contributor

ianayl commented Oct 15, 2025

File delete LGTM, I totally forgot about the aggregate workflow. Thanks for doing the clean up!

@lukaszstolarczuk
Copy link
Contributor Author

@intel/llvm-gatekeepers , can you please merge? build_run_native_cpu_e2e_tests test is not related to my changes around benchmarks

@steffenlarsen
Copy link
Contributor

Unexpectedly Passed Tests (1):
SYCL :: Regression/barrier_with_work.cpp

Reported in #20142. Looks to be flaky, so it should be made UNSUPPORTED.

@steffenlarsen steffenlarsen merged commit ac17c7c into intel:sycl Oct 16, 2025
27 of 28 checks passed
@lukaszstolarczuk lukaszstolarczuk deleted the benchmarks-scripts branch October 16, 2025 11:23
steffenlarsen added a commit to steffenlarsen/llvm that referenced this pull request Oct 16, 2025
As observed in intel#20369, the
Regression/barrier_with_work.cpp E2E test may pass sporadically. As such
it should be made UNSUPPORTED instead of XFAIL.

Signed-off-by: Larsen, Steffen <[email protected]>
againull pushed a commit that referenced this pull request Oct 17, 2025
As observed in #20369, the
Regression/barrier_with_work.cpp E2E test may pass sporadically. As such
it should be made UNSUPPORTED instead of XFAIL.

Signed-off-by: Larsen, Steffen <[email protected]>
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