Commit Graph

8 Commits

Author SHA1 Message Date
GitLab Bot 80f61b4035 Add latest changes from gitlab-org/gitlab@master 2019-09-18 14:02:45 +00:00
Thong Kuah 8c42a0eac0 Add frozen_string_literal to lib part 2
Using the sed script from
https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
2019-08-23 00:15:24 +12:00
Rémy Coutable b11e887582
Improve the architecture of RspecFlaky classes by introducing a new RspecFlaky::Report class
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-04-10 15:38:40 +02:00
Rémy Coutable 5bef32195b
Introduce RspecFlaky::ExamplesPruner to prune old flaky examples
Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-04-10 15:38:40 +02:00
Rémy Coutable cf62c96adc
Ensure we set SUITE_FLAKY_RSPEC_REPORT_PATH to nil in RspecFlaky::Listener spec
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-10-06 19:57:42 +02:00
Rémy Coutable da5aa64f06
Add new RSpecFlaky::FlakyExamplesCollection and RSpecFlaky::Config classes
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-10-06 12:00:09 +02:00
Rémy Coutable ebfb5a5075 Ensure RSpecFlaky doesn't automatically update flaky examples
Previously, instantiating a RspecFlaky::FlakyExample object would
automatically update its first_flaky_at, last_flaky_at and
last_flaky_job.

That was wrong because we would overwrite every time the suite report
with this false data.

We now:

- Get the suite report and only read from it
- Write only the currently detected flaky examples in the report, so
  that the final report is only updated with flaky examples that were
  actually detected in each job. Before, job1 could overwrite the legit
  report from job2!
- Write the newly detected flaky examples by rejecting the already
  tracked flaky specs instead of using another hash.

Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-10-04 15:14:38 +02:00
Rémy Coutable 8f8fd34231 Use a new RspecFlakyListener to detect flaky specs
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-08-11 14:55:10 +02:00