Skip to content

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

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 #112

Triggered via pull request July 5, 2024 03:42
Status Success
Total duration 14m 41s
Artifacts

test.yaml

on: pull_request
unit_test
19s
unit_test
integration_test_ubuntu
9m 22s
integration_test_ubuntu
integration_test_macos
14m 31s
integration_test_macos
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
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/