Skip to content

Log RSS when we're printing RSpec elapsed time

Lin Jen-Shin requested to merge 434955-log-rss-in-tests-in-ci into master

What does this MR do and why?

Log RSS when we're printing RSpec elapsed time

This is to help diagnose #434955 (closed)

Example: https://gitlab.com/gitlab-org/gitlab/-/jobs/5753708943

# [RSpecRunTime] Finishing example group spec/features/profiles/list_users_comment_template_spec.rb. It took 1.69 seconds. Expected to take 2.76 seconds.
# [RSpecRunTime] RSpec elapsed time: 21 minutes 20.07 seconds. Current RSS: ~1531M
# [RSpecRunTime] Starting example group spec/features/merge_requests/user_views_closed_merge_requests_spec.rb. Expected to take 1.65 seconds.
User views closed merge requests
  shows closed merge requests
# [RSpecRunTime] Finishing example group spec/features/merge_requests/user_views_closed_merge_requests_spec.rb. It took 1.18 seconds. Expected to take 1.65 seconds.
# [RSpecRunTime] RSpec elapsed time: 21 minutes 21.29 seconds. Current RSS: ~1527M

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

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.

Related to #434955 (closed)

Edited by Lin Jen-Shin

Merge request reports