You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
── Failure (test-backend-postgres.R:341:3): casts `y` column for local df ──────
... %>% collect() (`actual`) not equal to `out` (`expected`).
actual vs expected
val
actual[1, ] 10
- actual[2, ] 20
+ expected[2, ] 10
`actual$val`: "10" "20"
`expected$val`: "10" "10"
── Failure (test-backend-postgres.R:367:3): casts `y` column for local df ──────
tbl(con, "df_x") %>% collect() (`actual`) not equal to `out` (`expected`).
actual vs expected
val
actual[1, ] 10
- actual[2, ] 20
+ expected[2, ] 10
`actual$val`: "10" "20"
`expected$val`: "10" "10"
Here's the last run where that test passed on 10/31 and the first where it failed on 11/06. Both have PostgreSQL 17.0 (Debian 17.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit, on Ubuntu 22.04.
I was able to replicate on Linux with pak::local_install_dev_deps(), then mirroring the GHA service with:
Seeing on GHA re: column casts with PostgreSQL:
Here's the last run where that test passed on 10/31 and the first where it failed on 11/06. Both have PostgreSQL 17.0 (Debian 17.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit, on Ubuntu 22.04.
I was able to replicate on Linux with
pak::local_install_dev_deps()
, then mirroring the GHA service with:sudo docker run --name postgres-dev \ -e POSTGRES_USER=postgres \ -e POSTGRES_PASSWORD=password \ -e POSTGRES_DB=test \ -p 5432:5432 \ -d postgres sudo docker exec postgres-dev pg_isready -U postgres
and:
Related to #965--I don't think the fix here is just a snap update.
The text was updated successfully, but these errors were encountered: