Fides ctl postgres dataset annotation coverage tests are failing
See original GitHub issueBug Description
Quite suddenly and without a clear cause, the annotation tests for postgres
have started failing.
Additional context
On a change that is completely unrelated, it seemed to start failing: link to failed job
This is the earliest one I could find, but there might be earlier ones
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Documentation: 15: 33.1. Running the Tests - PostgreSQL
The tests will be run in a database named regression ; any existing database by this name will be dropped. The tests will...
Read more >Database settings - GitLab Docs
gitlab-ctl restart postgresql. If PostgreSQL fails to start, check the logs (for example, /var/log/gitlab/postgresql/current ) for more details.
Read more >How to setup Github Actions for Go + Postgres to run ...
Cover image for How to setup Github Actions for Go + Postgres to ... tests will still fail because it cannot connect to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think this might have a simpler answer based on my initial sniff test… when inspecting this, the failures are:
I call that out because @ThomasLaPiana and I definitely were making some updates to the default test PostgreSQL schema in other PRs, like this: https://github.com/ethyca/fides/pull/1609/files#diff-b649d6f7bfd020601ed8c65679441f25e5fe3c986d95fda02b4ec15e4cd10169
I think one possible explanation is that these “external” tests don’t run in CI unless you apply the
run-unsafe-checks
label and we weren’t doing that.Thank you all!
Ok, I’ll think more on this solution and ship a fix within the sprint 🙂