From 2939c61f7236c289e5f2fd828cbcb3ffb816c9c6 Mon Sep 17 00:00:00 2001 From: Rodolfo Alonso Hernandez Date: Tue, 12 Dec 2017 13:35:58 +0000 Subject: Remove "flake8" and "pep8" from test-requirements Removed "flake8" and "pep8" from test-requirements. Since 44070670c798d2cde2824f3150b2b11bf35c6319, "pylint" is the code style checker, instead of "flake8" or "pep8". JIRA: YARDSTICK-832 Change-Id: Iee598b0b1793d71dc74be36fa1875387b17d1e25 Signed-off-by: Rodolfo Alonso Hernandez --- docs/testing/developer/devguide/devguide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/testing/developer/devguide/devguide.rst') diff --git a/docs/testing/developer/devguide/devguide.rst b/docs/testing/developer/devguide/devguide.rst index 4f69456fc..00cef5739 100755 --- a/docs/testing/developer/devguide/devguide.rst +++ b/docs/testing/developer/devguide/devguide.rst @@ -361,7 +361,7 @@ Verify your patch locally before submitting Once you finish a patch, you can submit it to Gerrit for code review. A developer sends a new patch to Gerrit will trigger patch verify job on Jenkins -CI. The yardstick patch verify job includes python flake8 check, unit test and +CI. The yardstick patch verify job includes python pylint check, unit test and code coverage test. Before you submit your patch, it is recommended to run the patch verification in your local environment first. -- cgit 1.2.3-korg