Skip to content
litevm test

fix hc.uuid null pointer bug #430

Sign in to view logs

fix hc.uuid null pointer bug

fix hc.uuid null pointer bug #430

Triggered via pull request October 15, 2024 23:33
@richl9richl9
synchronize #119
richl9:richard/dm
Status Success
Total duration 10m 49s
Artifacts –

litevm.yml

on: pull_request
commit-hooks
55s
commit-hooks
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
commit-hooks
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/