After adding our small zynq uboot which has hush parser off these 3 tests
start to failed. It is probably just coincidence that others are
passing without hush parser.

Signed-off-by: Michal Simek <michal.si...@xilinx.com>
---

Not sure if this is the right dependency but would be great if someone
can test it too.

---
 test/py/tests/test_env.py | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/test/py/tests/test_env.py b/test/py/tests/test_env.py
index b7f960c755fe..05e57c3f04c4 100644
--- a/test/py/tests/test_env.py
+++ b/test/py/tests/test_env.py
@@ -188,6 +188,7 @@ def test_env_unset_non_existent(state_test_env):
     unset_var(state_test_env, var)
     validate_empty(state_test_env, var)
 
+@pytest.mark.buildconfigspec('hush_parser')
 def test_env_set_non_existent(state_test_env):
     """Test set a non-existant variable."""
 
@@ -196,6 +197,7 @@ def test_env_set_non_existent(state_test_env):
     set_var(state_test_env, var, value)
     validate_set(state_test_env, var, value)
 
+@pytest.mark.buildconfigspec('hush_parser')
 def test_env_set_existing(state_test_env):
     """Test setting an existant variable."""
 
@@ -212,6 +214,7 @@ def test_env_unset_existing(state_test_env):
     unset_var(state_test_env, var)
     validate_empty(state_test_env, var)
 
+@pytest.mark.buildconfigspec('hush_parser')
 def test_env_expansion_spaces(state_test_env):
     """Test expanding a variable that contains a space in its value."""
 
-- 
1.9.1

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to