1. 12 11月, 2019 24 次提交
  2. 11 11月, 2019 14 次提交
    • P
      util: pci: Remove always-false condition · e39d3424
      Peter Krempa 提交于
      Commit d19c2142 modified the condition so that it checks whether the
      value is more than 0xFFFFFFFF. Since addr->domain is an unsigned int, it
      will never be more than that.
      
      Remove the whole check
      
      src/util/virpci.c:1291:22: error: result of comparison 'unsigned int' > 4294967295 is always false [-Werror,-Wtautological-type-limit-compare]
          if (addr->domain > 0xFFFFFFFF) {
              ~~~~~~~~~~~~ ^ ~~~~~~~~~~
      Signed-off-by: NPeter Krempa <pkrempa@redhat.com>
      e39d3424
    • P
      tests: make domaincapstest less anoying to debug · 63d60408
      Peter Krempa 提交于
      Since 6a077cf2 domaincapstest does not run through all cases on
      failure but terminates right away. This makes it super annoying to debug
      or use in combination with VIR_TEST_REGENERATE_OUTPUT.
      
      Fix it by remembering failure and still running through all cases.
      Signed-off-by: NPeter Krempa <pkrempa@redhat.com>
      Reviewed-by: NDaniel Henrique Barboza <danielhb413@gmail.com>
      63d60408
    • D
      build: fix substitution of RUNSTATEDIR in man pages · d64f31dc
      Daniel P. Berrangé 提交于
      When RUNSTATEDIR was introduced
      
        commit d29c917e
        Author: Daniel P. Berrangé <berrange@redhat.com>
        Date:   Tue Aug 20 16:05:12 2019 +0100
      
          src: honour the RUNSTATEDIR variable in all code
      
      The makefile rules for man pages were accidentally not updated for the
      new variablle name.
      Reviewed-by: NAndrea Bolognani <abologna@redhat.com>
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      d64f31dc
    • D
      build: comment on why we're not adopting certain flake8 rules · 07943d35
      Daniel P. Berrangé 提交于
      Simplify the list of ignored warnings now that we only have two left,
      and document why we're not honouring them.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      07943d35
    • D
      python: sanitize indentation after line continuations · 3df69e62
      Daniel P. Berrangé 提交于
      Line continuations should be 4 space indented unless a previous opening
      brace required different alignment.
      
      docs/apibuild.py:2014:24: E126 continuation line over-indented for hanging indent
                             token[0], token[1]))
                             ^
      docs/apibuild.py:74:3: E121 continuation line under-indented for hanging indent
        "ATTRIBUTE_UNUSED": (0, "macro keyword"),
        ^
      ...more...
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      3df69e62
    • D
      python: sanitize spaces either side of operators · 43d29cb4
      Daniel P. Berrangé 提交于
      There should be a single space either side of operators. Inline
      comments should have two spaces before the '#'
      
      src/hyperv/hyperv_wmi_generator.py:130:45: E261 at least two spaces before inline comment
                  source += '    { "", "", 0 },\n' # null terminated
                                                  ^
      src/esx/esx_vi_generator.py:417:25: E221 multiple spaces before operator
          FEATURE__DESERIALIZE  = (1 << 6)
                              ^
      tests/cputestdata/cpu-cpuid.py:187:78: E225 missing whitespace around operator
                      f.write("  <msr index='0x%x' edx='0x%08x' eax='0x%08x'/>\n" %(
                                                                                   ^
      docs/apibuild.py:524:47: E226 missing whitespace around arithmetic operator
                                  self.line = line[i+2:]
                                                    ^
      ...more...
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      43d29cb4
    • D
      python: sanitize blank line usage · bc59247d
      Daniel P. Berrangé 提交于
      Coding style expects 1 blank line between each method and 2 blank lines
      before each class.
      
      docs/apibuild.py:171:5: E303 too many blank lines (2)
          def set_header(self, header):
          ^
      docs/apibuild.py:230:1: E302 expected 2 blank lines, found 1
      class index:
      ^
      docs/apibuild.py:175:5: E301 expected 1 blank line, found 0
          def set_module(self, module):
          ^
      ...more...
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      bc59247d
    • D
      python: avoid bare 'except:' clause · 2ba699cb
      Daniel P. Berrangé 提交于
      Exception catching statements should always match on a class name, the
      most specific one possible. Rather than analyse the code to look at what
      the most specific one is, this just uses the base Exception class.
      
      docs/apibuild.py:255:9: E722 do not use bare 'except'
              except:
              ^
      docs/apibuild.py:279:9: E722 do not use bare 'except'
              except:
              ^
      ...more...
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      2ba699cb
    • D
      python: avoid variable named 'l' · cfdd871f
      Daniel P. Berrangé 提交于
      Python code style recommends avoiding a variable named 'l' as it is
      visually similar to '1'.
      
      docs/apibuild.py:482:13: E741 ambiguous variable name 'l'
                  l = len(line)
                  ^
      docs/apibuild.py:503:21: E741 ambiguous variable name 'l'
                          l = len(line)
                          ^
      ...more...
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      cfdd871f
    • D
      python: mark regex strings with 'r' prefix · d5c5d8af
      Daniel P. Berrangé 提交于
      When writing regexes special regex matches like "\d" can get
      misinterpreted as normal string escape sequences:
      
      docs/apibuild.py:1359:51: W605 invalid escape sequence '\d'
                              value = value + re.sub("^(\d+)U$", "\\1", token[1])
                                                        ^
      docs/apibuild.py:2134:31: W605 invalid escape sequence '\('
                      m = re.match("\(?1<<(\d+)\)?", info[0])
                                    ^
      docs/apibuild.py:2134:38: W605 invalid escape sequence '\d'
                      m = re.match("\(?1<<(\d+)\)?", info[0])
                                           ^
      docs/apibuild.py:2134:42: W605 invalid escape sequence '\)'
                      m = re.match("\(?1<<(\d+)\)?", info[0])
                                               ^
      
      To avoid this probem all regexes should use the r"...." syntax for their
      strings, which disables normal string escape sequences.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      d5c5d8af
    • D
      python: fix use of undeclared variables in python scripts · 524b377e
      Daniel P. Berrangé 提交于
      docs/apibuild.py:2436:65: F821 undefined name 'first_letter'
                              chunks.append(["chunk%s" % (chunk - 1), first_letter, letter])
                                                                      ^
      src/hyperv/hyperv_wmi_generator.py:415:57: F821 undefined name 'number'
              report_error("line %d: invalid block header" % (number))
                                                              ^
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      524b377e
    • D
      build: change flake8 to use blacklist instead of whitelist · 3a5fea60
      Daniel P. Berrangé 提交于
      The current flake8 check only looks at one item (semicolons at end of
      line). This means that our code quality will continue to get worse,
      violating an increasing number of checks.
      
      Switching to a whitelist means that we freeze the badness at its
      current level & can incrementally fix things up.
      
      We are excluding the following...
      
      Indentation:
      
        E114 indentation is not a multiple of four (comment)
        E115 expected an indented block (comment)
        E116 unexpected indentation (comment)
        E121 continuation line under-indented for hanging indent
        E125 continuation line with same indent as next logical line
        E126 continuation line over-indented for hanging indent
        E127 continuation line over-indented for visual indent
        E128 continuation line under-indented for visual indent
        E129 visually indented line with same indent as next logical line
        E131 continuation line unaligned for hanging indent
      
      Whitespace:
      
        E211 whitespace before ‘(‘
        E221 multiple spaces before operator
        E222 multiple spaces after operator
        E225 missing whitespace around operator
        E226 missing whitespace around arithmetic operator
        E231 missing whitespace after ‘,’, ‘;’, or ‘:’
        E261 at least two spaces before inline comment
      
      Blank lines
      
        E301 expected 1 blank line, found 0
        E302 expected 2 blank lines, found 0
        E303 too many blank lines (3)
        E305 expected 2 blank lines after end of function or class
      
      Line length
      
        E501 line too long (82 > 79 characters)
      
      Statements
      
        E722 do not use bare except, specify exception instead
        E741 do not use variables named ‘l’, ‘O’, or ‘I’
      
      Errors:
      
        F821 undefined name 'name'
      
      Warnings:
      
        W504 line break after binary operator
        W605 invalid escape sequence ‘x’
      
      Later commits will enable most of these exclusions.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      3a5fea60
    • D
      55cbe0fb
    • P
      spec: fix rpm build with VPATH · c4192960
      Pavel Hrdina 提交于
      Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
      Reviewed-by: NErik Skultety <eskultet@redhat.com>
      c4192960
  3. 10 11月, 2019 1 次提交
  4. 09 11月, 2019 1 次提交