Skip to content
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

Postrges test fails consistently #567

Open
Rots opened this issue Sep 25, 2020 · 1 comment
Open

Postrges test fails consistently #567

Rots opened this issue Sep 25, 2020 · 1 comment

Comments

@Rots
Copy link
Contributor

Rots commented Sep 25, 2020

New Issue

Context

  • Operating System: Linux Mint 20

  • GoCryptoTrader version (gocryptotrader -version):
    GoCryptoTrader v0.1 amd64 go1.15.1 pre-release.

Expected Behavior

Running go tests locally pass.
If the target environment is not available for some tests, they should be skipped.

Current Behavior

tests consistently fail

Failure Information (for bugs)

make test fails

Steps to Reproduce / Failure Logs

gocryptotrader$ go test -v ./database/models/postgres/
Unable to execute setup: parameter validation failed:
        Parameter is an empty string: psql.user
        Parameter is an empty string: psql.host
        Parameter is an empty string: psql.dbname
FAIL    github.com/thrasher-corp/gocryptotrader/database/models/postgres        0.005s
FAIL
@xtda
Copy link
Contributor

xtda commented Sep 25, 2020

yeah this is caused by it looking for either sqlboiler.json or env vars on start up due to usage of viper

there are a few other minor issues with the template generation from our fork of sqlboiler such as a few of the other tests it will generate with FK relations will always fail and style related

I have been meaning to go through and update the fork to keep it inline with master
I think in the end i ended up finding local workrounds for almost all the issues besides one migration related so shouldn't be that much of an issue to keep it inline and also apply a fix to skip tests a lot more will get on it at some point this week hopefully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants