Skip to content

fix: 🐛 migration utils for mulit databases on same host #33

fix: 🐛 migration utils for mulit databases on same host

fix: 🐛 migration utils for mulit databases on same host #33

Triggered via pull request January 7, 2025 12:07
Status Failure
Total duration 9m 12s
Artifacts

elixir.yml

on: pull_request
Static checks (format, credo, dialyzer)
9m 2s
Static checks (format, credo, dialyzer)
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 32 warnings
Build and test (ce_test, postgres:16): test/plausible_web/controllers/api/external_stats_controller/query_test.exs#L3467
test metrics all metrics for breakdown by event prop (PlausibleWeb.Api.ExternalStatsController.QueryTest)
Build and test (ce_test, postgres:16)
Process completed with exit code 2.
Build and test (test, postgres:16)
The job was canceled because "ce_test_postgres_16_0" failed.
Build and test (test, postgres:16)
The operation was canceled.
Build and test (test, postgres:15)
The job was canceled because "ce_test_postgres_16_0" failed.
Build and test (test, postgres:15)
The operation was canceled.
Build and test (test, postgres:16, experimental_reduced_joins)
The job was canceled because "ce_test_postgres_16_0" failed.
Build and test (test, postgres:16, experimental_reduced_joins)
The operation was canceled.
Build and test (ce_test, postgres:16)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build and test (ce_test, postgres:16)
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 (ce_test, postgres:16)
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 (ce_test, postgres:16)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (ce_test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (ce_test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (ce_test, postgres:16)
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 (test, postgres:16)
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 (test, postgres:16)
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 (test, postgres:16)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16)
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 (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 (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
Build and test (test, postgres:15)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:15)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:15)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (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 (test, postgres:16, experimental_reduced_joins)
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 (test, postgres:16, experimental_reduced_joins)
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 (test, postgres:16, experimental_reduced_joins)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Build and test (test, postgres:16, experimental_reduced_joins)
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
Static checks (format, credo, dialyzer)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Static checks (format, credo, dialyzer)
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
Static checks (format, credo, dialyzer)
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
Static checks (format, credo, dialyzer)
l..r inside match is deprecated, you must always match on the step: l..r//var or l..r//_ if you want to ignore it
Static checks (format, credo, dialyzer)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Static checks (format, credo, dialyzer)
min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it
Static checks (format, credo, dialyzer)
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