Skip to content
test CI

fix: ecu_status: should use any_child_ecu_in_update flag instead of any_in_update to avoid self-lockedown, still wait on any_child_ecu_in_update before reboot #791

Sign in to view logs

fix: ecu_status: should use any_child_ecu_in_update flag instead of any_in_update to avoid self-lockedown, still wait on any_child_ecu_in_update before reboot

fix: ecu_status: should use any_child_ecu_in_update flag instead of any_in_update to avoid self-lockedown, still wait on any_child_ecu_in_update before reboot #791

Triggered via pull request December 18, 2024 07:51
@Bodong-YangBodong-Yang
synchronize #459
fix/ecu_status_any_in_update
Status Failure
Total duration 20m 24s
Artifacts –

test.yaml

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

Annotations

6 errors
pytest_with_coverage (ubuntu-18.04)
The job running on runner GitHub Actions 48 has exceeded the maximum execution time of 20 minutes.
pytest_with_coverage (ubuntu-18.04)
The operation was canceled.
pytest_with_coverage (ubuntu-22.04)
The job running on runner GitHub Actions 58 has exceeded the maximum execution time of 20 minutes.
pytest_with_coverage (ubuntu-22.04)
The operation was canceled.
pytest_with_coverage (ubuntu-20.04)
The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 20 minutes.
pytest_with_coverage (ubuntu-20.04)
The operation was canceled.