- 05 Oct, 2017 1 commit
-
-
Alessio Caiazza authored
-
- 12 Sep, 2017 1 commit
-
-
Maxim Rydkin authored
-
- 22 Jul, 2017 1 commit
-
-
Nick Thomas authored
-
- 21 Jul, 2017 1 commit
-
-
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.
-
- 20 Jul, 2017 1 commit
-
-
Douwe Maan authored
24570 use re2 for user supplied regexp 9 3 See merge request !2129
-
- 24 May, 2017 15 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
- 18 Apr, 2017 3 commits
-
-
Filipa Lacerda authored
-
Lin Jen-Shin authored
-
- 17 Apr, 2017 4 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 13 Apr, 2017 2 commits
-
-
Lin Jen-Shin authored
then it's fine to skip the first line because it won't be very noticeable
-
Lin Jen-Shin authored
of breaking ANSI sequence or Unicode
-
- 12 Apr, 2017 1 commit
-
-
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.
-
- 06 Apr, 2017 1 commit
-
-
Kamil Trzciński authored
-