fix: Snapshots as starting point for eventsBySlices, take 2 #1551
build-test.yml
on: pull_request
Checks
3m 4s
Run test with Postgres
4m 16s
Run test with Postgres and JSONB payload
2m 3s
Run test with Postgres and several data partitions
4m 0s
Run tests with Yugabyte
5m 8s
Run test with H2
3m 53s
Run test with SQL Server
4m 25s
Docs
1m 50s
Annotations
32 warnings
|
Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0xFB3aQAAAABhdW4iZqU7Q74B90yclPrLRE0yRURHRTEwMTUARWRnZQ==
|
|
Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0w1B3aQAAAAClqPieEa6wQYo/1ct0zPMvRE0yRURHRTEwMTUARWRnZQ==
|
|
Docs
Failed to restore: Cache service responded with 400
|
|
Docs
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres and JSONB payload
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0FFF3aQAAAADW9zWPJbzgRIXW4PsXRYNBRE0yRURHRTA3MTcARWRnZQ==
|
|
Run test with Postgres and JSONB payload
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0E1F3aQAAAAC5qavpTy8KSoslpPljvzZYRE0yRURHRTA3MTcARWRnZQ==
|
|
Run test with Postgres and JSONB payload
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres and JSONB payload
Failed to restore: Cache service responded with 400
|
|
Checks
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0TFF3aQAAAADiweqcV6fySLY+amLAh8wwRE0yRURHRTA0MTgARWRnZQ==
|
|
Checks
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0S1F3aQAAAACWwlO7gdsaSJxO+T0QY0iRRE0yRURHRTA0MTgARWRnZQ==
|
|
Checks
Failed to restore: Cache service responded with 400
|
|
Checks
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres and several data partitions
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0eVF3aQAAAADAdm0M1YaIT4hqien59n9ORE0yRURHRTA5MjIARWRnZQ==
|
|
Run test with Postgres and several data partitions
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0eVF3aQAAAABBvG8TH48sQ4oYyistfbzDRE0yRURHRTA5MjIARWRnZQ==
|
|
Run test with Postgres and several data partitions
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres and several data partitions
Failed to restore: Cache service responded with 400
|
|
Run test with H2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0flF3aQAAAACHsdowUeHWTqk0yAzM/ayERE0yRURHRTAxMTQARWRnZQ==
|
|
Run test with H2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0fVF3aQAAAAAgoNIBb/YiQaZ+sooU/eD9RE0yRURHRTAxMTQARWRnZQ==
|
|
Run test with H2
Failed to restore: Cache service responded with 400
|
|
Run test with H2
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0klF3aQAAAACXKUOUyZ0CS73/6KpFT81aUEhYMzFFREdFMDYxNQBFZGdl
|
|
Run test with Postgres
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0kVF3aQAAAAC+xaVLVU+bSo22qcj/U634UEhYMzFFREdFMDYxNQBFZGdl
|
|
Run test with Postgres
Failed to restore: Cache service responded with 400
|
|
Run test with Postgres
Failed to restore: Cache service responded with 400
|
|
Run test with SQL Server
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0m1F3aQAAAAB/vFTZPL7nRLT4eolg8WHXRE0yRURHRTA5MTIARWRnZQ==
|
|
Run test with SQL Server
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0m1F3aQAAAABvVsRSh1R3T7BeNLJw10M/RE0yRURHRTA5MTIARWRnZQ==
|
|
Run test with SQL Server
Failed to restore: Cache service responded with 400
|
|
Run test with SQL Server
Failed to restore: Cache service responded with 400
|
|
Run tests with Yugabyte
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0x1F3aQAAAACmUZge3YJaQbXUDLlroPiwRE0yRURHRTA3MTAARWRnZQ==
|
|
Run tests with Yugabyte
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0x1F3aQAAAAC50bIuwQk2QbMrRwP8EN10RE0yRURHRTA3MTAARWRnZQ==
|
|
Run tests with Yugabyte
Failed to restore: Cache service responded with 400
|
|
Run tests with Yugabyte
Failed to restore: Cache service responded with 400
|