-
Notifications
You must be signed in to change notification settings - Fork 787
[CI][SYCL-CTS] Ensure link/test runs are parallel #13533
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
#13421 reduced parellization when trying to avoid early build failouts. Use `ninja`'s `-k0` to do the same without undesired side effects.
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.
Definitely much better, but it would be helpful to have a list of failed to build categories in the summary. Anyway, it may be tricky, so we can left it for the future.
c75c6cf
to
2ef17a6
Compare
BTW - there is a "test_conformance" target to build all except |
Manual testing runs: |
@intel/dpcpp-devops-reviewers this is ready for your review. |
@steffenlarsen @cperkinsintel @uditagarwal97 @intel/dpcpp-devops-reviewers , ping x2. |
https://github.com/intel/llvm/actions/runs/8821781116/job/24220570301?pr=13533 |
Yes, we only run it in Nightly. Also, it's "either e2e or cts", that particular job was running e2e. |
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!
Failures are unrelated - they are on e2e and not on cts. |
#13421 reduced parellization when trying to avoid early build failouts. Use
ninja
's-k0
to do the same without undesired side effects. Also run individual tests in parallel as well.