Hi Tom, Thanks for pointing that out. I've done a little investigation, and the interesting thing is that it never fails when I exclude other tests, for example, running only ut_dm subset: ./test/py/test.py --bd sandbox_flattree --build -s -k ut_dm or even this particular test: ./test/py/test.py --bd sandbox_flattree --build -s -k ut_dm_tee
Each time it fails in the same place on trying to allocate a hashtree (using hash tree funcs from /lib/hashtable.c) with 20 elements when probing tee device, and seems that it just a consequence of that fact, that some functionality, which tested before tee, is not doing a proper cleanup (when full testing is done). Anyway, I can decrease the number of elements for the hashtree, but it definitely won't fix the root cause. Regards, Igor On Sat, 9 Feb 2019 at 14:50, Tom Rini <tr...@konsulko.com> wrote: > > On Sun, Jan 27, 2019 at 04:34:05PM +0200, Igor Opaniuk wrote: > > > AVB version 1.1 introduces support for named persistent values > > that must be tamper evident and allows AVB to store arbitrary key-value > > pairs [1]. > > > > Introduce implementation of two additional AVB operations > > read_persistent_value()/write_persistent_value() for retrieving/storing > > named persistent values. > > > > Correspondent pull request in the OP-TEE OS project repo [2]. > > > > [1]: > > https://android.googlesource.com/platform/external/avb/+/android-9.0.0_r22 > > [2]: https://github.com/OP-TEE/optee_os/pull/2699 > > > > Signed-off-by: Igor Opaniuk <igor.opan...@linaro.org> > > Reviewed-by: Simon Glass <s...@chromium.org> > > The test fails on some sandbox targets: > https://travis-ci.org/trini/u-boot/jobs/490809872 > > -- > Tom -- Regards, Igor Opaniuk _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot