From: Simon Glass <sjg@chromium.org>
Date: Sat, 6 Aug 2022 23:51:54 +0000 (-0600)
Subject: test: Make test_gpio_read() independent
X-Git-Tag: v2023.07~312^2~21^2~5
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=b681669aa533346b648995ae8c4bd9d257ea920a;p=platform%2Fkernel%2Fu-boot.git

test: Make test_gpio_read() independent

This assumes that the GPIO starts as 0 but it does not if
test_gpio_input() ran first and test_gpio_exit_statuses() was skipped.
This can happen when running tests in parallel.

Fix it.

Signed-off-by: Simon Glass <sjg@chromium.org>
---

diff --git a/test/py/tests/test_gpio.py b/test/py/tests/test_gpio.py
index fa0af5f..0af186f 100644
--- a/test/py/tests/test_gpio.py
+++ b/test/py/tests/test_gpio.py
@@ -51,6 +51,7 @@ def test_gpio_exit_statuses(u_boot_console):
 def test_gpio_read(u_boot_console):
     """Test that gpio read correctly sets the variable to the value of a gpio pin."""
 
+    u_boot_console.run_command('gpio clear 0')
     response = u_boot_console.run_command('gpio read var 0; echo val:$var,rc:$?')
     expected_response = 'val:0,rc:0'
     assert(expected_response in response)