Skip to content

fix: TAP-10570 Multi-update operations are not allowed when updating … #2064

fix: TAP-10570 Multi-update operations are not allowed when updating …

fix: TAP-10570 Multi-update operations are not allowed when updating … #2064

Triggered via pull request March 31, 2026 04:26
@mnianqimnianqi
synchronize #747
TAP-10570
Status Failure
Total duration 1m 27s
Artifacts

mr-ci.yaml

on: pull_request
Get-Current-Branch
3s
Get-Current-Branch
Get-Stable-Branch
15s
Get-Stable-Branch
Sync-Code-to-Office
1m 1s
Sync-Code-to-Office
Scan-Connectors
0s
Scan-Connectors
Fit to window
Zoom out
Zoom in

Annotations

1 error and 10 warnings
Sync-Code-to-Office
Final attempt failed. Child_process exited with error code 255
Get-Current-Branch
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/
Get-Stable-Branch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
Get-Stable-Branch
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/
Get-Stable-Branch
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/
Get-Stable-Branch
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/
Get-Stable-Branch
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/
Get-Stable-Branch
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/
Sync-Code-to-Office
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/checkout@v3, nick-fields/retry@v2. 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/
Sync-Code-to-Office
Attempt 2 failed. Reason: Child_process exited with error code 255
Sync-Code-to-Office
Attempt 1 failed. Reason: Child_process exited with error code 255