Hello Tom,
On Thu, Sep 12, 2024 at 11:45:01AM -0600, Tom Rini wrote:
On Thu, Sep 12, 2024 at 10:10:53AM +0300, Dmitry Rokosov wrote:
There are Pipeline results. One test was failed. I suppose it's not related to my patch series:
https://github.com/u-boot/u-boot/pull/625/checks?check_run_id=30029925059
=================================== FAILURES =================================== _______________________ test_ut[ut_dm_dm_test_rtc_dual] ________________________ test/py/tests/test_ut.py:590: in test_ut assert output.endswith('Failures: 0') E AssertionError: assert False E + where False = <built-in method endswith of str object at 0x7fb0835c50d0>('Failures: 0') E + where <built-in method endswith of str object at 0x7fb0835c50d0> = 'Test: dm_test_rtc_dual: rtc.c\r\r\nTest: dm_test_rtc_dual: rtc.c (flat tree)\r\r\ntest/dm/rtc.c:307, dm_test_rtc_dual...&now1, &cmp, false): Expected 0xffffffea (-22), got 0x0 (0)\r\r\nTest dm_test_rtc_dual failed 1 times\r\r\nFailures: 1'.endswith ----------------------------- Captured stdout call ----------------------------- => ut dm dm_test_rtc_dual
Test: dm_test_rtc_dual: rtc.c
Test: dm_test_rtc_dual: rtc.c (flat tree)
test/dm/rtc.c:307, dm_test_rtc_dual(): -EINVAL == cmp_times(&now1, &cmp, false): Expected 0xffffffea (-22), got 0x0 (0)
Test dm_test_rtc_dual failed 1 times
Failures: 1
=> =================================== FAILURES ===================================
Yes, sometimes that just fails due to the underlying hardware (even with retries). Please tell it to try again so that the world build tests run. Sorry for the noise here.
Thank you for the comments. I have re-run the pipeline. Once it is finished, I will provide the results here.