-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] Run multiple triples at once in check-sycl #10635
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
Conversation
67450ef
to
cf06453
Compare
We don't have complex rules in those tests so it should be easy to update the tests to support this scenario. It should save use about 2-3 out of 8 minutes for the `check-sycl` target by reducing number of host compilations.
cf06453
to
c09a236
Compare
looks unrelated as nothing about E2E tests has been changed here. Reviewers (@intel/dpcpp-esimd-reviewers , @intel/llvm-reviewers-runtime , @steffenlarsen), ping. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
esimd lgtm
Single triple targets are only meant for manual run and should not be included into check-all, only check-sycl-combined-triples should be. Otherwise we are running the same tests from multiple processes resulting in race conditions (beside unnecessary work).
Single triple targets are only meant for manual run and should not be included into check-all, only check-sycl-combined-triples should be. Otherwise we are running the same tests from multiple processes resulting in race conditions (beside unnecessary work).
We don't have complex rules in those tests so it is easy to update the tests to support this scenario. It should save us about 2-3 out of 8-10 minutes for the `check-sycl` target by reducing number of host compilations.
Single triple targets are only meant for manual run and should not be included into check-all, only check-sycl-combined-triples should be. Otherwise we are running the same tests from multiple processes resulting in race conditions (beside unnecessary work).
We don't have complex rules in those tests so it is easy to update the
tests to support this scenario. It should save us about 2-3 out of
8-10 minutes for the
check-sycl
target by reducing number of hostcompilations.