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
..
api/helpers
banzai	Make the "customizes the whitelist only once" spec less brittle	2017-09-22 12:00:02 -04:00
bitbucket
constraints
container_registry	Prevent new / renamed project from using a repository path that already exists on disk	2017-08-25 20:06:06 +02:00
github	Fix notes type created from import	2017-09-29 11:18:58 +00:00
gitlab	Merge branch 'gitaly-fetch-ref' into 'master'	2017-10-04 12:07:17 +00:00
json_web_token
mattermost
microsoft_teams
rspec_flaky	Ensure RSpecFlaky doesn't automatically update flaky examples	2017-10-04 15:14:38 +02:00
system_check	Whitelist authorized_keys.lock in the gitlab:check rake task	2017-10-02 11:25:02 +01:00
additional_email_headers_interceptor_spec.rb
after_commit_queue_spec.rb
disable_email_interceptor_spec.rb
event_filter_spec.rb
expand_variables_spec.rb
extracts_path_spec.rb
feature_spec.rb
file_size_validator_spec.rb
gitlab_spec.rb
repository_cache_spec.rb
system_check_spec.rb