Reset all connection schema cache after migration tests (!14195) · Merge requests · GitLab.org / GitLab FOSS · GitLab

Do not update/delete: Banner broadcast message test data

Do not update/delete: Notification broadcast message test data

username-removed-423915 requested to merge 37608-reset-all-connections into master Sep 11, 2017

What does this MR do?

Reset all connection schema cache after migration tests

Are there points in the code the reviewer needs to double check?

Could we also reduce the number of connections for tests? No, 1 is not enough though.

Why was this MR needed?

Try to tackle https://gitlab.com/gitlab-org/gitlab-ce/issues/37608

This could explain why it's somehow random. Rails could checkout a random connection in the pool.

Does this MR meet the acceptance criteria?

Review
- Has been reviewed by Backend
- Has been reviewed by Database

What are the relevant issue numbers?

See #37608 (closed)