Skip to content

Fix JointFabricDatastore ownership, lifetime, and sync edge cases #152275

Fix JointFabricDatastore ownership, lifetime, and sync edge cases

Fix JointFabricDatastore ownership, lifetime, and sync edge cases #152275

Triggered via pull request April 9, 2026 18:40
@vijsvijs
synchronize #71453
vijs:fix/0407
Status Success
Total duration 43m 9s
Artifacts

build.yaml

on: pull_request
Build on Linux (gcc_debug)
21m 3s
Build on Linux (gcc_debug)
Build on Linux (fake, gcc_release, clang, simulated)
43m 4s
Build on Linux (fake, gcc_release, clang, simulated)
Build on Linux (python_lib)
33m 24s
Build on Linux (python_lib)
Build on Linux (python lighting-app)
7m 4s
Build on Linux (python lighting-app)
Build on Darwin (clang, simulated)
15m 36s
Build on Darwin (clang, simulated)
Build on Linux (coverage)
36m 0s
Build on Linux (coverage)
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
Build on Linux (python lighting-app)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build on Linux (python lighting-app)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (python lighting-app)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Build on Darwin (clang, simulated)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build on Darwin (clang, simulated)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (gcc_debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build on Linux (gcc_debug)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (gcc_debug)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Build on Linux (python_lib)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build on Linux (python_lib)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (python_lib)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Build on Linux (coverage)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build on Linux (coverage)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (fake, gcc_release, clang, simulated)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build on Linux (fake, gcc_release, clang, simulated)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (fake, gcc_release, clang, simulated)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.