-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e2e test passing CI but actually failing #186
Labels
Type: Technical issue
Improve something that users won't notice
Comments
mrjones-plip
added
the
Type: Technical issue
Improve something that users won't notice
label
Nov 15, 2024
mrjones-plip
changed the title
e2e test actually failing but still passing CI
e2e test passing CI but actually failing
Nov 15, 2024
Digging into the docker logs, I see this error in postgres:
That's coming from this query: const dbtReports = await pgClient.query(`SELECT * FROM ${pgSchema}.reports`); So
If these can't be different, maybe there should only be one variable, not two? Then all but 2 tests pass:
|
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
On the
main
branch, when we run thewaitForDbt(client)
it should succeed, but it fails with an error (see below). Further, CI actually succeeds instead of noticing that there was an error.Describe the improvement you'd like
We should fail the CI test if it fails in CI. We should also fix the test so it succeeds (and so does CI then).
Describe alternatives you've considered
NA
The text was updated successfully, but these errors were encountered: