You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logging this here, because I have not seen this fail before and it is likely (very) intermittent only -- TIMEOUTFAULT0002 got stuck on this run. The corresponding commit had no code changes, so definitely did not introduce an error.
Wed, 31 Jan 2024 04:01:07 GMT <testcase classname="sel4test" name="TIMEOUTFAULT0002">
Wed, 31 Jan 2024 04:14:21 GMT
Wed, 31 Jan 2024 04:14:21 GMT [[Timeout]]
The failing config was ODROID_XU4_release_MCS_clang_32 on the board odroidxu4_1.
Might be a hardware fluke, just logging it here in case it is related to something else.
The text was updated successfully, but these errors were encountered:
That's that dodgy Odroid board again, isn't it? I don't trust that hardware, and hence won't spend timing debugging problems on it. Could you change CI so it's using odroidxu4_2 instead? If it happens there too, we have more assurance it's not just broken hardware.
Logging this here, because I have not seen this fail before and it is likely (very) intermittent only --
TIMEOUTFAULT0002
got stuck on this run. The corresponding commit had no code changes, so definitely did not introduce an error.The failing config was
ODROID_XU4_release_MCS_clang_32
on the boardodroidxu4_1
.Might be a hardware fluke, just logging it here in case it is related to something else.
The text was updated successfully, but these errors were encountered: