Skip to content

Use kernelSpecs to explicitly instantiate fluid models and resolve CUDA builds #16936

Use kernelSpecs to explicitly instantiate fluid models and resolve CUDA builds

Use kernelSpecs to explicitly instantiate fluid models and resolve CUDA builds #16936

Triggered via pull request June 10, 2026 19:17
Status Success
Total duration 1h 58m 25s
Artifacts

ci_tests.yml

on: pull_request
is_not_draft_pull_request
5s
is_not_draft_pull_request
resolve_ci_provider
5s
resolve_ci_provider
Matrix: check_code_style_and_documentation
if_not_unassigned_pull_request
7s
if_not_unassigned_pull_request
are_submodules_in_sync
16s
are_submodules_in_sync
check_code_rules
12s
check_code_rules
baseline_log
9s
baseline_log
Matrix: cpu_builds
Matrix: cuda_builds
run_integrated_tests  /  build_test_deploy
51m 5s
run_integrated_tests / build_test_deploy
check_that_all_jobs_succeeded
3s
check_that_all_jobs_succeeded
Fit to window
Zoom out
Zoom in

Annotations

1 warning
check_code_rules
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/