Skip to content
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

Increase math builtin test fragment size #975

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

steffenlarsen
Copy link
Contributor

Currently the CI for the SYCL CTS is failing for DPC++ due to a timeout. This commit attempts to find a sweet-spot for the fragmentation size of math builtin test, balancing compilation resources and compilation time.

Currently the CI for the SYCL CTS is failing for DPC++ due to a timeout.
This commit attempts to find a sweet-spot for the fragmentation size
of math builtin test, balancing compilation resources and compilation
time.

Signed-off-by: Larsen, Steffen <[email protected]>
@steffenlarsen steffenlarsen marked this pull request as ready for review November 5, 2024 08:45
@steffenlarsen steffenlarsen requested a review from a team as a code owner November 5, 2024 08:45
@tomdeakin
Copy link
Contributor

What does that CMake option do?

@steffenlarsen
Copy link
Contributor Author

What does that CMake option do?

The option is for controlling the number of math builtin test permutations being put into the same source-file. The intention is to find the sweet-spot for parallelizing the compilation. I would like to see this be a top-level option when configuring the CTS eventually, but for now the intention is to try and avoid the CI timing out.

@@ -44,7 +44,7 @@ foreach(cat ${MATH_CAT})
FILE_PREFIX "math_builtin_${cat}"
EXT "cpp"
INPUT "math_builtin.template"
EXTRA_ARGS -test ${cat} -marray true -fragment-size 150
EXTRA_ARGS -test ${cat} -marray true -fragment-size 230
Copy link
Member

Choose a reason for hiding this comment

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

While you are here, you could factorized out this function or macro and add your PR comment as a code comment. 😄

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