Skip to content

[CI] Switch post-commit jobs to self-hosted runners #5147

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

Merged
merged 1 commit into from
Dec 15, 2021

Conversation

alexbatashev
Copy link
Contributor

Should not be a problem with the increased machine count

@alexbatashev alexbatashev requested a review from bader as a code owner December 15, 2021 08:48
Copy link
Contributor

@bader bader left a comment

Choose a reason for hiding this comment

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

How about switching linux_clang_shared_libs too?

@alexbatashev
Copy link
Contributor Author

How about switching linux_clang_shared_libs too?

Plan is to re-write it completely as part of #5130

@bader bader merged commit 2d55e8f into intel:sycl Dec 15, 2021
@bader
Copy link
Contributor

bader commented Dec 15, 2021

How about switching linux_clang_shared_libs too?

Plan is to re-write it completely as part of #5130

Okay, but I must say that this exactly configuration fails on GitHub machines.

@alexbatashev
Copy link
Contributor Author

How about switching linux_clang_shared_libs too?

Plan is to re-write it completely as part of #5130

Okay, but I must say that this exactly configuration fails on GitHub machines.

Failures that I see are all build failures. They're not failing due to timeouts.

@bader
Copy link
Contributor

bader commented Dec 15, 2021

Okay, let's see post-commit results for 18df116. I guess it should fix the build problem you are referring to. @sergey-semenov, am I right?

@sergey-semenov
Copy link
Contributor

@bader The warnings that 18df116 addresses are part of that, but when I look at the post-commit results for the previous commit I see other warnings unrelated to that coming from the CUDA plugin: https://github.com/intel/llvm/runs/4533614173?check_suite_focus=true, so I'm pretty sure 18df116 won't be enough.

@bader
Copy link
Contributor

bader commented Dec 15, 2021

Thanks for clarification. I think CUDA plug-in issue is exposed by a95c12a, which added testing of new configuration for CUDA and HIP plug-ins - with disabled assertions.

alexbatashev added a commit to alexbatashev/llvm that referenced this pull request Dec 15, 2021
* upstream/sycl: (5961 commits)
  [SYCL] Implement discard_events extension (intel#5026)
  [SYCL][NFC] Fix unused parameter warning in piQueueFlush (intel#5139)
  [SYCL][XPTI] Fix static analysis tool warnings (intel#5040)
  [CI] Switch post-commit jobs to self-hosted runners (intel#5147)
  [SYCL] Fix support for classes implicitly converted from items in parallel_for (intel#5118)
  [SYCL][HIP] Fix platform query in USM alloc info (intel#5140)
  [Docker] Add workarounds for two SYCL issues (intel#5143)
  [CI] Install cm-compiler in drivers image (intel#5128)
  [ESIMD] Add support for an arbitrary number of elements to simd::copy_from/to (intel#5135)
  [SYCL] Add number HW threads per EU query (intel#4901)
  [CI] Refactor workflow files (intel#5134)
  [CI] Enable HIP and CUDA plugins in GitHub Actions builds (intel#5087)
  [SYCL] Implement queue flushing (intel#5052)
  Disable issue labeler in LLVM forks
  Modify translation for disable_loop_pipelining metadata
  Add SPIR-V friendly translation for OpLoad and OpStore
  Fix return type postfix for SPIR-V Friendly IR
  Restrict special handling of sampler OpVariable only to UniformConstant
  Add lowering for llvm.bswap intrinsic
  Fix translation of OpVariable with OpSamplerType
  ...
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.

3 participants