Skip to content

fix: Fix can not find the correct parent node with the same name #110

fix: Fix can not find the correct parent node with the same name

fix: Fix can not find the correct parent node with the same name #110

Triggered via pull request July 4, 2024 13:46
Status Failure
Total duration 13m 31s
Artifacts

test.yaml

on: pull_request
unit_test
23s
unit_test
integration_test_ubuntu
9m 35s
integration_test_ubuntu
integration_test_macos
13m 21s
integration_test_macos
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
integration_test_ubuntu
Process completed with exit code 1.
integration_test_macos
Process completed with exit code 1.
unit_test
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration_test_ubuntu
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration_test_macos
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/