Skip to content
Validate and test

fix: Snapshots as starting point for eventsBySlices, take 2 #1549

Sign in to view logs

fix: Snapshots as starting point for eventsBySlices, take 2

fix: Snapshots as starting point for eventsBySlices, take 2 #1549

Triggered via pull request January 20, 2026 07:56
@patriknwpatriknw
synchronize #717
wip-start-snapshot2-patriknw
Status Failure
Total duration 6m 23s
Artifacts –

build-test.yml

on: pull_request
Checks
2m 24s
Checks
Run test with Postgres
4m 19s
Run test with Postgres
Run test with Postgres and JSONB payload
2m 22s
Run test with Postgres and JSONB payload
Run test with Postgres and several data partitions
3m 56s
Run test with Postgres and several data partitions
Run tests with Yugabyte
5m 21s
Run tests with Yugabyte
Run test with H2
3m 57s
Run test with H2
Run test with SQL Server
4m 20s
Run test with SQL Server
Docs
1m 33s
Docs
Fit to window
Zoom out
Zoom in

Annotations

1 error and 30 warnings
Checks
Process completed with exit code 1.
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>05DVvaQAAAACyl/lFFHRcQICGsWOLbsEERE0yRURHRTAxMTcARWRnZQ==
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>04zVvaQAAAADtvEDWqafcRroKYXtmlHbVRE0yRURHRTAxMTcARWRnZQ==
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>0DzZvaQAAAABq/pX2cYwaR66Eowdf7Di1UEhYMzFFREdFMDUxNwBFZGdl
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>0DjZvaQAAAACxQ67lkkaPRr2mprPj+yjbUEhYMzFFREdFMDUxNwBFZGdl
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 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>0MzZvaQAAAADq07hWtnuMRYAqBXTJzPugRE0yRURHRTA4MTMARWRnZQ==
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>0MzZvaQAAAADHLuUCLh9tSIl/NJ19KqOIRE0yRURHRTA4MTMARWRnZQ==
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 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>0TDZvaQAAAACYujt677G4T52xmVX4uyf9RE0yRURHRTA3MTAARWRnZQ==
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>0SzZvaQAAAACXdf8uC2RoToyKt2zQd+0eRE0yRURHRTA3MTAARWRnZQ==
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 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>0czZvaQAAAAAHEDT4WeaKRL8fzM1ZEifNRE0yRURHRTA5MjIARWRnZQ==
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>0czZvaQAAAACgvpAYpJMnQIrgBlGRxveIRE0yRURHRTA5MjIARWRnZQ==
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>0ijZvaQAAAADBF0n87z6jRJR1FlyX/SD5RE0yRURHRTA5MDgARWRnZQ==
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>0iTZvaQAAAABMp3U9AtNRTah92zvWDUNKRE0yRURHRTA5MDgARWRnZQ==
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 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>0wjZvaQAAAAAi4omScluDRrMIOexizdbHRE0yRURHRTA0MjAARWRnZQ==
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>0wjZvaQAAAABOPtF5n4y3RJOlPJtHHJdCRE0yRURHRTA0MjAARWRnZQ==
Run tests with Yugabyte
Failed to restore: Cache service responded with 400
Run tests with Yugabyte
Failed to restore: Cache service responded with 400