Skip to content

Failing tests on duckdb #203

@RasmusSkytte

Description

@RasmusSkytte

Describe the bug
Recently, tests started failing on https://github.com/ssi-dk/diseasystore and https://github.com/ssi-dk/diseasy on the duckdb backend.

I have tracked these failures to a change I have made in our testing pipeline where I set the time-zone of the testing machines to a different time-zone than ours (specifically to the Sydney/Australia) with the specific purpose of triggering uncaught time-zone related issues.

It seems that this has worked in this case, although it took me some time to put it together.

Tests were failing on Github but worked fine on my machine and I did not connect this to the changes to the testing pipeline (the error messages on diseasystore and diseasy were also sufficiently unrelated to timestamps for me to figure it out easily).

Rather nicely, the new docker images in the test pipeline were very useful since I could download them and get a local copy where the issue could be reproduced.

To Reproduce
Run the tests in the docker images from the failing tests

Expected behaviour
N/A

Screenshots
N/A

Provide output from sessionInfo()
N/A

  • I have checked that the bug is not already described in open issues

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions