On 5/3/25 11:19, Heinrich Schuchardt wrote:
On 5/2/25 16:50, Simon Glass wrote:
Hi Heinrich,
On Thu, 1 May 2025 at 22:13, Heinrich Schuchardt <xypron.g...@gmx.de>
wrote:
Am 2. Mai 2025 03:38:36 MESZ schrieb Simon Glass <s...@chromium.org>:
Hi,
On Tue, 14 Jan 2025 at 23:56, Hal Feng <hal.f...@starfivetech.com>
wrote:
On 09.01.25 20:37, Simon Glass wrote:
Hi,
I am seeing a lab failure on this board with the test_dm_compat
test[1]:
=================================== FAILURES
===================================
559________________________________ test_dm_compat
________________________________
560test/py/tests/test_dm.py:20: in test_dm_compat
561 assert not bad_drivers
562E AssertionError: assert not {'starfive_gpio'}
Would you have time to take a look, please? A patch to fix a
similar problem
on another board is [2].
Regards,
Simon
[1] https://ci.u-boot.org/u-boot/u-boot/-/jobs/14394
[2]
https://patchwork.ozlabs.org/project/uboot/
patch/20240611200156.224552
5-19-...@chromium.org/
I will take a look. Thanks.
I just wanted to check if you sent a patch and if so, if you have a
link to it please?
Regards,
SImon
Hello Simon,
The error in the log [1] is
"Writing U-Boot using method riscv
cat: /sys/class/block/sdaa13/size: No such file or directory"
I would expect a partition on a block device to be called sda13 not
sdaa13.
Could this be a bug in your lab test script?
(Ubuntu uses partition 13 on the SD-card for U-Boot SPL.)
No, that's just something it prints when waiting for the device to
appear. Perhaps I should suppress it.
The real error is below:
________________________________ test_dm_compat
________________________________
560test/py/tests/test_dm.py:20: in test_dm_compat
561 assert not bad_drivers
562E AssertionError: assert not {'starfive_gpio'}
It would be *great* if someone could fix it, as it always fails in my
lab and I have to manually check it.
Regards,
Simon
With current upstream U-Boot when executed manually the output of dm
tree is:
gpio 0 [ + ] starfive_gpio | | `-- starfive_gpio
The output of dm compat is:
starfive_gpio
According to the test description this should be just fine.
Best regards
Heinrich
In my lab the test passes on the VF2 board:
Accessing Gembird #1 USB device 002
Switched outlet 3 off
+u-boot-test-flash starfive_visionfive2 na
... /home/zfsdt/workspace/u-boot-build/u-boot-test/u-boot-test-flash ...
Accessing Gembird #1 USB device 002
Switched outlet 3 on
=============================================== test session starts
===============================================
platform linux -- Python 3.12.3, pytest-7.4.4, pluggy-1.4.0
rootdir: /home/zfsdt/workspace/u-boot-build/denx/test/py
configfile: pytest.ini
plugins: cov-4.1.0, xdist-3.4.0
collected 763 items / 762 deselected / 1 selected
test/py/tests/test_dm.py .
[100%]
======================================= 1 passed, 762 deselected in
12.73s ========================================
+u-boot-test-release starfive_visionfive2 na
... /home/zfsdt/workspace/u-boot-build/u-boot-test/u-boot-test-release ...
Accessing Gembird #1 USB device 002
Switched outlet 3 off
Best regards
Heinrich
