Skip to content
Python tests

Add rendering for fruit_tree env #354

Sign in to view logs

Add rendering for fruit_tree env

Add rendering for fruit_tree env #354

Re-run triggered January 18, 2024 22:51
@LucasAlegreLucasAlegre
#81
tomekster:ts/add_fruit_tree_env_render
Status Success
Total duration 4m 20s
Artifacts –

test.yml

on: pull_request
Matrix: linux-test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
linux-test (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
linux-test (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
linux-test (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
linux-test (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/