1. 08 6月, 2017 3 次提交
  2. 07 6月, 2017 5 次提交
  3. 06 6月, 2017 2 次提交
  4. 01 6月, 2017 1 次提交
  5. 31 5月, 2017 4 次提交
  6. 30 5月, 2017 11 次提交
  7. 29 5月, 2017 6 次提交
  8. 26 5月, 2017 7 次提交
    • C
      docstring directives: define more formal and strict format · 1719d983
      Cleber Rosa 提交于
      The format of the docstring directives has not been formally described
      so far.  Because at least two different features are built on that,
      and possibly more will come, it's a good idea to define a format.
      
      This introduces a stricter format, basically adding a number of
      requirements or rules.  To make the following description more
      consistent let's call the "🥑" part of the docstring directive
      "the marker" and what follows it the "content".
      
      1) One or more spaces are required between the "🥑" marker and
         the content.  The following is a valid docstring directive:
      
         "🥑 enable"
      
         While this is invalid:
      
         ":avocado:enable"
      
      2) A more limited set of characters are now allowed in the content,
         namely one from the following set: [a-zA-Z0-9_:,=].  The following
         is a valid docstring directive:
      
         "🥑 foo=bar,foz=baz:extra"
      
         While the following is invalid:
      
         "🥑 foo=bar!"
      
      3) The first character of the content must be alphanumeric, so the
         following is a valid docstring directive:
      
         "🥑 foo=bar"
      
         While the following is invalid:
      
         "🥑 =bar"
      
      4) An end of string (or end of line) is now required after the content
         (which itself may not contain white spaces).  The following is a
         valid docstring directive:
      
         "🥑 enable"
      
         While the following is invalid:
      
         "🥑 enable FOO"
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      1719d983
    • L
      runner: Try to interrupt test gently first · 97f032ff
      Lukáš Doktor 提交于
      When the test does not produces the early_status in 60s or when the test
      pushes the final status and not exits we SIGKILL the test, leaving us
      with no trace on where it might hang. Let's use SIGTERM first and wait
      for 1s to see whether the process won't be able to give us traceback,
      otherwise nuke it with SIGKILL as before.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      97f032ff
    • L
      runner: Raise RuntimeError instead of SystemExit · ba5c0956
      Lukáš Doktor 提交于
      The SystemExit exception does not produce the traceback, let's use
      RuntimeError instead to be able to tell where the test was interrupted.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      ba5c0956
    • A
      utils/memory.py : function to get the linux page size · fd4166f8
      Abdul Haleem 提交于
      Added a function to get the linux page size for the given
      kernel, it returns a byte value from 'getconf PAGESIZE'
      command.
      
      systems can have 4k, 64k page sizes, accordingly decide to
      start a memory tests.
      Signed-off-by: NAbdul Haleem <abdhalee@linux.vnet.ibm.com>
      fd4166f8
    • L
      Merging pull request 2034 · 478617a1
      Lukáš Doktor 提交于
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      
      * https://github.com/avocado-framework/avocado:
        avocado/core/mux.py: use hashlib for Python 3 support
        selftests/functional/test_loader.py: use mode definition
        selftests/functional/test_lv_utils.py: use print function from future
        avocado/core/dispatcher.py: do not require a configuration file
        avocado/core/output.py: default to colored output
        Settings: also handle unexisting sections
      478617a1
    • A
      selftests: remove redundant test · 6cb2f710
      Amador Pahim 提交于
      with the new 'test_statuses.py', this test became redundant.
      Signed-off-by: NAmador Pahim <apahim@redhat.com>
      6cb2f710
    • A
      test: always execute tearDown() · 2c571c7d
      Amador Pahim 提交于
      Currently, when something goes wrong in setUp(), tearDown() is not
      executed. This patch changes the behaviour of our Test class, making the
      tearDown() to be always executed, regardless what happens in setUp().
      
      Reference: https://trello.com/c/zSZ4xFwpSigned-off-by: NAmador Pahim <apahim@redhat.com>
      2c571c7d
  9. 25 5月, 2017 1 次提交