On 2/21/19 4:45 PM, Stephen Warren wrote:
With the latest push to u-boot.git master branch, I'm seeing the
following failures running test/py on sandbox:
=> ut dm pch_base
Test: dm_test_pch_base: pch.c
/var/lib/jenkins/workspace/u-boot-denx_uboot-master-build/src/u-boot/test/dm/pch.c:20,
dm_test_pch_base(): 0 == uclass_first_device_err(UCLASS_PCH, &dev):
Expected 0, got -19
Test: dm_test_pch_base: pch.c (flat tree)
/var/lib/jenkins/workspace/u-boot-denx_uboot-master-build/src/u-boot/test/dm/pch.c:20,
dm_test_pch_base(): 0 == uclass_first_device_err(UCLASS_PCH, &dev):
Expected 0, got -19
Failures: 2
=> ut dm pch_ioctl
Test: dm_test_pch_ioctl: pch.c
/var/lib/jenkins/workspace/u-boot-denx_uboot-master-build/src/u-boot/test/dm/pch.c:44,
dm_test_pch_ioctl(): 0 == uclass_first_device_err(UCLASS_PCH, &dev):
Expected 0, got -19
Test: dm_test_pch_ioctl: pch.c (flat tree)
/var/lib/jenkins/workspace/u-boot-denx_uboot-master-build/src/u-boot/test/dm/pch.c:44,
dm_test_pch_ioctl(): 0 == uclass_first_device_err(UCLASS_PCH, &dev):
Expected 0, got -19
Failures: 2
This is some kind of incremental build problem; I deleted the build
results and retriggered Jenkins and everything worked fine. The exact
same issue and solution appeared and worked in two separate branches
that I test (u-boot.git master, u-boot-video.git master). Subsequently I
found that the following works fine:
rm -rf build-sandbox/
git checkout 888f9aa5cac4
./test/py/test.py --bd sandbox --build -k test_ut
But the following reproduces the problem:
rm -rf build-sandbox/
git checkout 97f9830849c6
./test/py/test.py --bd sandbox --build -k test_ut
git checkout 888f9aa5cac4
./test/py/test.py --bd sandbox --build -k test_ut
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
