Skip to content

Add deep dive view and 20x query performance improvement #199

Add deep dive view and 20x query performance improvement

Add deep dive view and 20x query performance improvement #199

Triggered via pull request April 22, 2026 13:53
Status Cancelled
Total duration 46m 21s
Artifacts 12

crucible-ci.yaml

on: pull_request
call-real-core-release-crucible-ci  /  gen-params
8s
call-real-core-release-crucible-ci / gen-params
call-faux-core-release-crucible-ci  /  core-release-crucible-ci-complete
call-faux-core-release-crucible-ci / core-release-crucible-ci-complete
call-real-core-release-crucible-ci  /  display-params
2s
call-real-core-release-crucible-ci / display-params
call-real-core-release-crucible-ci  /  build-controller
5s
call-real-core-release-crucible-ci / build-controller
Matrix: call-real-core-release-crucible-ci / call-core-crucible-ci
call-real-core-release-crucible-ci  /  core-release-crucible-ci-complete
0s
call-real-core-release-crucible-ci / core-release-crucible-ci-complete
crucible-ci-complete
3s
crucible-ci-complete
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 19 warnings, and 130 notices
crucible-ci-complete
Process completed with exit code 1.
crucible-ci
Canceling since a higher priority waiting request for refs/pull/181/merge/crucible-ci exists
crucible-ci
Canceling since a higher priority waiting request for refs/pull/181/merge/crucible-ci exists
crucible-ci
Canceling since a higher priority waiting request for refs/pull/181/merge/crucible-ci exists
crucible-ci
Canceling since a higher priority waiting request for refs/pull/181/merge/crucible-ci exists
changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
call-real-core-release-crucible-ci / gen-params
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
call-real-core-release-crucible-ci / build-controller
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / gen-endpoints(upstream)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / gen-params(upstream, kube)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (remotehosts) / gen-params(upstream, remotehosts)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (remotehosts) / runners (sleep, true, remotehosts, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / runners (hwnoise, true, kube, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / runners (sleep, true, kube, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (remotehosts) / runners (fio, true, remotehosts, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / runners (fio, true, kube, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (remotehosts) / runners (iperf, true, remotehosts, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (remotehosts) / runners (multi, true, remotehosts, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / runners (cyclictest, true, kube, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / runners (iperf, true, kube, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / runners (uperf, true, kube, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / runners (multi, true, kube, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (kube) / runners (oslat, true, kube, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. 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/
call-real-core-release-crucible-ci / call-core-crucible-ci (upstream) / call-core-endpoint-crucible-ci (remotehosts) / runners (uperf, true, remotehosts, self-hosted, aws-cloud-1, default)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/

Artifacts

Produced during runtime
Name Size Digest
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__kube__cyclictest-default-upstream Expired
7.88 MB
sha256:bb973c1d6779372ad9b1a036d5cbc299974dbbb30a998ffd197120d6d8936a5e
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__kube__fio-default-upstream Expired
6.04 MB
sha256:3b6b1967978422fee0750a9f6da95357ce3b4ab515b1fd1bf22a1b4b8ad6ac04
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__kube__hwnoise-default-upstream Expired
3.59 MB
sha256:b5c5e1e190eeb383b0f0c403619ed897e0bf99f6f384626c57f49862068fa1cf
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__kube__iperf-default-upstream Expired
6.96 MB
sha256:39ff413c610f38c4e88bd1f9784fdf7b00c523d4ffaa9ce8c4eb7c7874451d94
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__kube__multi-default-upstream Expired
7.13 MB
sha256:df7ea9f9f59889867c57650756c4c6a28eb5f7bdcbaa2456dc29bd97c68f3b0c
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__kube__oslat-default-upstream Expired
6.97 MB
sha256:36f8d9a9802a3edad812afe07c382dd8f968ce2cc71be4bece25c4a00229b1e3
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__kube__sleep-default-upstream Expired
3.58 MB
sha256:403210f730d8d17fcf2ac08329daa31f7f8d4ea511f62fec37eec958bc3fdf41
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__kube__uperf-default-upstream Expired
7.9 MB
sha256:49a81a16404f2417497f1f2ab9edcea99aec26d303e353246f8532c53024c807
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__remotehosts__fio-default-upstream Expired
6.94 MB
sha256:1381557ca72ccfc6c545bb9a30a0e51031d32ab7c318165bb81d320233dfce66
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__remotehosts__iperf-default-upstream Expired
7.77 MB
sha256:6ab7b911a774240860755ec607b7c0c9fd45384195bbc1709a756451f741bea8
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__remotehosts__multi-default-upstream Expired
7.82 MB
sha256:001292b0d238fd707047ac770452d218ff7859fbc1c131bbaf93f9b0e3b1d959
crucible-ci-artifact__integration-tests__199.1__CommonDataModel__remotehosts__sleep-default-upstream Expired
4.14 MB
sha256:0e119770802ab324f71b135f19fac3ea4b507bf8b1e48065a0fbfb90f2553e61