Skip to content

fix: Fix total retry time from reconnnection attempts (#2306) #2230

fix: Fix total retry time from reconnnection attempts (#2306)

fix: Fix total retry time from reconnnection attempts (#2306) #2230

Re-run triggered February 6, 2025 11:03
Status Failure
Total duration 2m 27s
Artifacts

elixir_tests.yml

on: push
Check formatting
12s
Check formatting
Matrix: build_and_test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 6 warnings
Build and test, Postgres 14
The job was canceled because "_17" failed.
Build and test, Postgres 15
test after restart restores publication filters (Electric.ShapeCacheTest)
Build and test, Postgres 15
Process completed with exit code 2.
Build and test, Postgres 14
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test, Postgres 14
62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead
Build and test, Postgres 17
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test, Postgres 17
62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead
Build and test, Postgres 15
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
Build and test, Postgres 15
62..@dynamic_table_start + length - 1 inside guards requires an explicit step, please write 62..@dynamic_table_start + length - 1//1 or 62..@dynamic_table_start + length - 1//-1 instead