Intermittent test errors with DuckDB

[gvegayon]

I am getting errors on testthat b/c of duckdb. The issue is intermittent, so either we are missing a seed, or there's something else going on. https://github.com/CDCgov/cfa-epinow2-pipeline/actions/runs/11943535928/job/33293099360#step:3:309. I have had to restart the job many times in the past, with the second try working. Unsure what's the issue

attn @natemcintosh @zsusswein

Originally posted by @gvegayon in #89 (comment)

[athowes]

I also got a similar error and documented in #119.

[zsusswein]

Yeah this is a recurring issue with a flaky test failures not due to any test but because of something going wrong with the DuckDB helper that writes test data files.

I need to look into more but, it always away when rerunning (i.e., it's not that frequent) so it's been lower priority than simply getting a v1 running.

It's definitely on my guilty list! Would love some help on it if you have any interest in investigating,

[athowes]

going wrong with the DuckDB helper that writes test data files.

Which function is this?

[zsusswein]

https://github.com/CDCgov/cfa-epinow2-pipeline/blob/main/tests/testthat/helper-write_parameter_file.R