Add latest changes from gitlab-org/gitlab@master

.gitlab/issue_templates/Experiment Successful Cleanup.md

@@ -0,0 +1,18 @@
+<!-- Title suggestion: [Experiment Name] Successful Cleanup -->
+
+## Summary
+
+The experiment is currently rolled out to 100% of users and has been deemed a success.
+The changes need to become an official part of the product.
+
+## Steps
+
+- [ ] Determine whether the feature should apply to SaaS and/or self-managed
+- [ ] Determine whether the feature should apply to EE - and which tiers - and/or Core
+- [ ] Determine if tracking should be kept as is, removed, or modified.
+- [ ] Migrate experiment to a default enabled [feature flag](https://docs.gitlab.com/ee/development/feature_flags/development.html) for one milestone and add a changelog. Converting to a feature flag can be skipped at the ICs discretion if risk is deemed low with consideration to both SaaS and (if applicable) self managed.
+- [ ] Ensure any relevant documentation has been updated.
+- [ ] In the next milestone, [remove the feature flag](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up).
+- [ ] After the flag removal is deployed, [clean up the feature/experiment feature flags](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up) by running chatops command in `#production` channel
+
+/label ~"feature" ~"feature::maintenance" ~"workflow::scheduling" ~"growth experiment" ~"feature flag"  

doc/administration/audit_events.md

@@ -190,14 +190,7 @@ The search filters you can see depends on which audit level you are at.
 ## Export to CSV **(PREMIUM ONLY)**
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1449) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.4.
-> - It's [deployed behind a feature flag](../user/feature_flags.md), disabled by default.
-> - It's disabled on GitLab.com.
-> - It's not recommended for production use.
-> - To use it in GitLab self-managed instances, ask a GitLab administrator to [enable it](#enable-or-disable-audit-log-export-to-csv). **(PREMIUM ONLY)**
-
-CAUTION: **Warning:**
-This feature might not be available to you. Check the **version history** note above for details.
-If available, you can enable it with a [feature flag](#enable-or-disable-audit-log-export-to-csv).
+> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/285441) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.7.
 
 Export to CSV allows customers to export the current filter view of your audit log as a
 CSV file, which stores tabular data in plain text. The data provides a comprehensive view with respect to
@@ -237,22 +230,3 @@ The first row contains the headers, which are listed in the following table alon
 
 The Audit Log CSV file is limited to a maximum of `100,000` events.
 The remaining records are truncated when this limit is reached.
-
-### Enable or disable Audit Log Export to CSV
-
-The Audit Log Export to CSV is under development and not ready for production use. It is
-deployed behind a feature flag that is **disabled by default**.
-[GitLab administrators with access to the GitLab Rails console](../administration/feature_flags.md)
-can enable it.
-
-To enable it:
-
-```ruby
-Feature.enable(:audit_log_export_csv)
-```
-
-To disable it:
-
-```ruby
-Feature.disable(:audit_log_export_csv)
-```

spec/tooling/lib/tooling/parallel_rspec_runner_spec.rb

@@ -43,6 +43,16 @@ RSpec.describe Tooling::ParallelRSpecRunner do # rubocop:disable RSpec/FilePath
 
         subject.run
       end
+
+      context 'when there is no intersect between allocated tests and filtered tests' do
+        let(:filter_tests) { '99_spec.rb' }
+
+        it 'does not run rspec' do
+          expect(subject).not_to receive(:exec)
+
+          subject.run
+        end
+      end
     end
 
     context 'with empty filter tests file' do

tooling/lib/tooling/parallel_rspec_runner.rb

@@ -38,6 +38,11 @@ module Tooling
       Knapsack.logger.info tests_to_run
       Knapsack.logger.info
 
+      if tests_to_run.empty?
+        Knapsack.logger.info 'No tests to run on this node, exiting.'
+        return
+      end
+
       exec(*rspec_command)
     end