Skip to content

Profilers should never use benchmark pod settings #36

Profilers should never use benchmark pod settings

Profilers should never use benchmark pod settings #36

Re-run triggered October 25, 2024 15:11
Status Success
Total duration 29m 28s
Artifacts 144

crucible-merged.yaml

on: pull_request_target
call-core-crucible-ci_if-merged  /  gen-params
12s
call-core-crucible-ci_if-merged / gen-params
call-core-crucible-ci_if-merged  /  display-params
4s
call-core-crucible-ci_if-merged / display-params
call-core-crucible-ci_if-merged  /  build-controller
5s
call-core-crucible-ci_if-merged / build-controller
Matrix: call-core-crucible-ci_if-merged / github-runners
Matrix: call-core-crucible-ci_if-merged / self-hosted-runners
call-core-crucible-ci_if-merged  /  core-crucible-ci-complete
4s
call-core-crucible-ci_if-merged / core-crucible-ci-complete
Fit to window
Zoom out
Zoom in

Annotations

1000 notices

Artifacts

Produced during runtime
Name Size
crucible-ci-artifact__integration-tests__36.2__rickshaw__github-runners__remotehost-uperf-alma8 Expired
3.34 MB
crucible-ci-artifact__integration-tests__36.2__rickshaw__self-hosted-runners__remotehost-cyclictest-rhubi9 Expired
3.14 MB
crucible-ci-artifact__integration-tests__36.2__rickshaw__self-hosted-runners__remotehost-oslat-stream9 Expired
3.09 MB