Skip to content

DMT: seg fault when user exits application during 'step 1/3 Connecting to the migration cluster...' [CLC-442] #47

DMT: seg fault when user exits application during 'step 1/3 Connecting to the migration cluster...' [CLC-442]

DMT: seg fault when user exits application during 'step 1/3 Connecting to the migration cluster...' [CLC-442] #47

Triggered via issue November 14, 2023 14:30
Status Success
Total duration 20s
Artifacts

jira.yml

on: issues
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
jira
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
jira
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
jira
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
jira
The following actions uses node12 which is deprecated and will be forced to run on node16: atlassian/gajira-login@v2.0.0, atlassian/gajira-create@v2.0.1, actions/github-script@v4.0.2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/