[U-Boot] [PATCH] test/py: hush_if_test: Add tests to cover octal/hex values

Michal Simek michal.simek at xilinx.com
Tue Oct 15 06:08:37 UTC 2019

Hi Simon,

On 11. 10. 19 17:53, Simon Glass wrote:
> Hi Michal,
> On Fri, 11 Oct 2019 at 01:50, Michal Simek <michal.simek at xilinx.com> wrote:
>> On 10. 10. 19 19:06, Simon Glass wrote:
>>> Hi Michal,
>>> On Thu, 10 Oct 2019 at 05:44, Michal Simek <michal.simek at xilinx.com> wrote:
>>>> Extend test suite to cover also automatic octal/hex converstions which
>>>> haven't been implemented in past.
>>>> Signed-off-by: Michal Simek <michal.simek at xilinx.com>
>>>> ---
>>>> Depends on https://lists.denx.de/pipermail/u-boot/2019-September/383309.html
>>>> There are of course other tests which we can run but not sure if make sense
>>>> to have there all combinations. The most interesting are mixed tests which
>>>> are failing before patch above is applied.
>>>> Definitely please let me know if you want to add any other test.
>>>> ---
>>>>  test/py/tests/test_hush_if_test.py | 27 +++++++++++++++++++++++++++
>>>>  1 file changed, 27 insertions(+)
>>> I worry that these tests might be very slow since it requires a lot of
>>> interaction with U-Boot over a pipe. Is it possible to put them in C
>>> code instead, e.g. cmd_ut?
>> I have of course running it on my HW and it is quite fast. It is just 16
>> more simple tests. And if this breaks gitlab/travis CI loops then we
>> have bigger problem.
> I mean running these tests on sandbox. The interactions with the
> sandbox command line are quite slow I think.

I am not sharing this concern.

[u-boot]$ time ./test/py/test.py --bd sandbox -s -k hush >/dev/null

real	0m2,403s
user	0m1,263s
sys	0m0,299s

[u-boot]$ time ./test/py/test.py --bd sandbox -s -k hush >/dev/null

real	0m2,864s
user	0m1,563s
sys	0m0,305s

And if 0.4s on testing will cause issues somewhere else we have
different kind of problem.


More information about the U-Boot mailing list