Skip to content

fix(ios, android): performance records inaccurate issues #2614

fix(ios, android): performance records inaccurate issues

fix(ios, android): performance records inaccurate issues #2614

Triggered via pull request July 22, 2024 03:24
@wwwcgwwwcg
synchronize #3960
wwwcg:main
Status Success
Total duration 6m 0s
Artifacts

android_build_tests.yml

on: pull_request
Matrix: android_build_tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
android_build_tests (debug, v8_min)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
android_build_tests (release, v8_target)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
android_build_tests (debug, v8_target)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
android_build_tests (release, v8_min)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/