U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Love Kumar <love.kumar@amd.com>
To: Andrew Goodbody <andrew.goodbody@linaro.org>, u-boot@lists.denx.de
Cc: Tom Rini <trini@konsulko.com>, michal Simek <michal.simek@amd.com>
Subject: Re: [PATCH] test/py: memtest: Fix test for non-trivial parameters
Date: Sun, 30 Mar 2025 16:10:45 +0530	[thread overview]
Message-ID: <4523d02c-bfca-4d75-b643-05cae8850a65@amd.com> (raw)
In-Reply-To: <20250328163037.24594-1-andrew.goodbody@linaro.org>



On 28/03/25 10:00 pm, Andrew Goodbody wrote:
> When using non-trivial values for parameters for this test it
> will cause a spurious failure as the test passes a decimal value
> to the mtest command which will interpret it as hexadecimal and
> result in failure as below.
> 
> test/py/tests/test_memtest.py:66: in test_memtest_ddr
>      assert expected_response in response
> E   AssertionError: assert 'Tested 16 iteration(s) with 0 errors.' in 'Refusing to do empty test\r\nmtest - simple RAM read/write test\r\n\r\nUsage:\r\nmtest [start [end [pattern [iterations]]]]'
> ----------------------------- Captured stdout call -----------------------------
> U-Boot> mtest 134217728 0x8001000 90 0x10
> Refusing to do empty test
> mtest - simple RAM read/write test
> Usage:
> mtest [start [end [pattern [iterations]]]]
> 
> The fix is to ensure that all the parameters to the mtest command are
> passed as hexadecimal values.
> 
> Fixes: 22efc1cf276c ("test/py: memtest: Add tests for mtest command")
> Signed-off-by: Andrew Goodbody <andrew.goodbody@linaro.org>
> 
> ---
> 
>   test/py/tests/test_memtest.py | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/test/py/tests/test_memtest.py b/test/py/tests/test_memtest.py
> index 0618d96f1be..f03e23db2e4 100644
> --- a/test/py/tests/test_memtest.py
> +++ b/test/py/tests/test_memtest.py
> @@ -29,12 +29,12 @@ def get_memtest_env(u_boot_console):
>       if not f:
>           pytest.skip("memtest is not enabled!")
>       else:
> -        start = f.get("start_addr", 0x0)
> -        size = f.get("size", 0x1000)
> -        pattern = f.get("pattern", 0x0)
> +        start = hex(f.get("start_addr", 0x0))
> +        size = hex(f.get("size", 0x1000))
> +        pattern = hex(f.get("pattern", 0x0))
>           iteration = f.get("iteration", 2)
>           timeout = f.get("timeout", 50000)
> -        end = hex(int(start) + int(size))
> +        end = hex(int(start, 16) + int(size, 16))
>           return start, end, pattern, iteration, timeout
>   
>   @pytest.mark.buildconfigspec("cmd_memtest")

Reviewed-by: Love Kumar <love.kumar@amd.com>


  reply	other threads:[~2025-03-30 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 16:30 [PATCH] test/py: memtest: Fix test for non-trivial parameters Andrew Goodbody
2025-03-30 10:40 ` Love Kumar [this message]
2025-04-10 20:14 ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4523d02c-bfca-4d75-b643-05cae8850a65@amd.com \
    --to=love.kumar@amd.com \
    --cc=andrew.goodbody@linaro.org \
    --cc=michal.simek@amd.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox