Use let_it_be in batched_mr_diffs_spec
What does this MR do and why?
Related #375006 (closed)
Describe in detail what your merge request does and why.
Before
Finished in 1 minute 6.99 seconds (files took 28.41 seconds to load)
4 examples, 0 failures, 1 pending
[TEST PROF INFO] Time spent in factories: 00:09.286 (10.7% of total time)
[TEST PROF INFO] Factories usage
Total: 10
Total top-level: 7
Total time: 00:09.286 (out of 01:31.398)
Total uniq factories: 4
total top-level total time time per call top-level time name
3 3 7.6883s 2.5628s 7.6883s project
3 0 0.5664s 0.1888s 0.0000s namespace
3 3 1.5911s 0.5304s 1.5911s merge_request
1 1 0.0068s 0.0068s 0.0068s license
After
Finished in 57.98 seconds (files took 9.05 seconds to load)
4 examples, 0 failures, 1 pending
[TEST PROF INFO] Time spent in factories: 00:03.319 (5.64% of total time)
[TEST PROF INFO] Factories usage
Total: 4
Total top-level: 3
Total time: 00:03.319 (out of 01:03.375)
Total uniq factories: 4
total top-level total time time per call top-level time name
1 1 0.0075s 0.0075s 0.0075s license
1 1 2.4986s 2.4986s 2.4986s project
1 0 0.1641s 0.1641s 0.0000s namespace
1 1 0.8131s 0.8131s 0.8131s merge_request
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.