An error occurred fetching the project authors.
  1. 17 Jun, 2019 1 commit
  2. 15 Mar, 2019 1 commit
  3. 27 Nov, 2018 1 commit
  4. 26 Apr, 2018 1 commit
  5. 06 Apr, 2018 2 commits
  6. 05 Apr, 2018 2 commits
  7. 15 Aug, 2017 1 commit
  8. 24 Jul, 2017 1 commit
  9. 22 Jul, 2017 1 commit
  10. 21 Jul, 2017 1 commit
    • Nick Thomas's avatar
      Fix the gcovr coverage regex by removing line separators before scanning · 000ddc96
      Nick Thomas authored
      RE2 differs from Ruby in handling multiple-line strings. The string "foo\n"
      will not match the regular expression "foo$" unless multi-line mode is enabled
      (and it's off by default).
      
      Since we're already scanning the build trace line by line (and so multi-line
      coverage regular expressions won't work), we can fix this by removing the line
      separator before scanning the string.
      000ddc96
  11. 20 Jul, 2017 1 commit
  12. 24 May, 2017 4 commits
  13. 18 Apr, 2017 1 commit
  14. 17 Apr, 2017 5 commits
  15. 13 Apr, 2017 2 commits
  16. 12 Apr, 2017 1 commit
    • Z.J. van de Weg's avatar
      Return nil as coverage instead of a File object · 23fbbe0c
      Z.J. van de Weg authored
      Given a valid pipeline job, and a regex which wouldn't match to a jobs
      trace, the stream of the trace would return the File object. This was
      not the case when it matched a value, as that would have been return
      from the block.
      
      Now the `extract_coverage` method returns `nil` if no match was found.
      23fbbe0c
  17. 06 Apr, 2017 1 commit