Skip to content

Fix: sync DB-generated values back to original models in CrudService.SaveChangesAsync #1985

Fix: sync DB-generated values back to original models in CrudService.SaveChangesAsync

Fix: sync DB-generated values back to original models in CrudService.SaveChangesAsync #1985

Re-run triggered March 13, 2026 12:49
Status Failure
Total duration 4m 9s
Artifacts 7

platform-ci.yml

on: pull_request
Matrix: deploy-cloud / Deploy
Waiting for pending jobs
ui-auto-tests  /  dry-run
ui-auto-tests / dry-run
ui-auto-tests  /  ui-autotests
4m 0s
ui-auto-tests / ui-autotests
platform-katalon-tests  /  e2e-tests
12m 1s
platform-katalon-tests / e2e-tests
trivy-scan  /  scan-and-process
trivy-scan / scan-and-process
owasp-scan
owasp-scan
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
ui-auto-tests / ui-autotests
Process completed with exit code 1.
ui-auto-tests / ui-autotests
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/setup-python@v5, actions/upload-artifact@v4, VirtoCommerce/vc-github-actions/setup-vcbuild@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
graphql-dataset-manager-log-chromium-1985-3
62 KB
sha256:358001e8ee07ca3ecadc1f0a136d7368f39aa58beb915b0845bee9c1bf6fba1c
graphql-test-results-chromium-1985-3
13.1 KB
sha256:de3834d7d0c5a54fdae55363d90009ea507b6fd45aec34ae7ef49d57a682e20f