Long-running replication tests
Problem
We need long-running stress tests for replication.
Summary of changes
Add them
Related to neondatabase/cloud#13390, neondatabase/cloud#14490, neondatabase/cloud#14724
3092 tests run: 2977 passed, 0 failed, 115 skipped (full report)
Code coverage* (full report)
-
functions:32.6% (6935 of 21279 functions) -
lines:50.0% (54525 of 109034 lines)
* collected from Rust tests only
5e109066e79df739d02f60d7b483c2477911d574 at 2024-07-07T09:34:33.528Z :recycle:
Let's merge this one, then change it to use the same project every time.
Use long-running queries, "start a transaction, query some tables, then use pg_sleep()".
Change transaction isolation level in tests.
@save-buffer is OOO for few days, so feel free to merge this
I'll take this over for Sasha while he is out.
I cleaned up the commit history, and I think got to all of the review comments. I also rebased on main. How can we test this to make sure I didn't screw it up touching everything up?
I cleaned up the commit history, and I think got to all of the review comments. I also rebased on main. How can we test this to make sure I didn't screw it up touching everything up?
Triggered it: https://github.com/neondatabase/neon/actions/runs/9784944626/job/27016926175
Fixed bad merge, a couple of missed issues and retriggered it here: https://github.com/neondatabase/neon/actions/runs/9785504530/job/27018662789
UPD: the test run looks good!
Good work on this everybody!
Ugh. @bayandin I just overwrote your commits rebasing on main to get the conclusion job. Can you add them back when you get a chance. I am such an idiot.
Can you add them back when you get a chance
No problem! Will do tomorrow (I'm afk for the rest of the day)
Please enjoy your weekend :)