From: Dylan Baker <baker.dyla...@gmail.com>
These tests claimed to test the timeout mechanism, but what they're
really testing is the status changing ability of the timeout mechanism.
Signed-off-by: Dylan Baker <dylanx.c.ba...@intel.com>
---
framework/tests/base_tests.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/framework/tests/base_tests.py b/framework/tests/base_tests.py
index c005273..a825e3d 100644
--- a/framework/tests/base_tests.py
+++ b/framework/tests/base_tests.py
@@ -67,7 +67,7 @@ def test_run_return_early():
@attr('slow')
def test_timeout():
- """test.base.Test.run(): kills tests that exceed timeout when set"""
+ """test.base.Test.run(): Sets status to 'timeout' when timeout exceeded"""
utils.binary_check('sleep', 1)
class _Test(Test):
@@ -82,7 +82,7 @@ def test_timeout():
@attr('slow')
def test_timeout_pass():
- """test.base.Test.run(): Result is returned when timeout is set but not
exceeded
+ """test.base.Test.run(): Doesn't change status when timeout not exceeded
"""
utils.binary_check('true')
--
2.6.2
_______________________________________________
Piglit mailing list
Piglit@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/piglit
