Skip to content
CI

ENG-428: Support flow.username for both live and batch modes #3417

Sign in to view logs

ENG-428: Support flow.username for both live and batch modes

ENG-428: Support flow.username for both live and batch modes #3417

Triggered via pull request October 23, 2024 13:44
@asvetlovasvetlov
synchronize #1175
asvetlov:flow-username
Status Failure
Total duration 3m 56s
Artifacts –

ci.yaml

on: pull_request
Linter
1m 3s
Linter
Matrix: Unit
Matrix: E2E
Check
0s
Check
Deploy on PyPI
0s
Deploy on PyPI
Fit to window
Zoom out
Zoom in

Annotations

8 errors
Unit (3.11, ubuntu)
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Unit (3.10, ubuntu)
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Unit (3.9, macos)
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Unit (3.12, macos)
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Unit (3.12, ubuntu)
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Unit (3.9, ubuntu)
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Unit (3.9, windows)
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.
Unit (3.12, windows)
The ssh-private-key argument is empty. Maybe the secret has not been configured, or you are using a wrong secret name in your workflow file.