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

build test failure: unable to find yaml config while it exists #64

Open
arcolife opened this issue Aug 1, 2018 · 1 comment
Open

build test failure: unable to find yaml config while it exists #64

arcolife opened this issue Aug 1, 2018 · 1 comment

Comments

@arcolife
Copy link
Collaborator

arcolife commented Aug 1, 2018

[test]              /src:/src/..
[test]              warning: "./trueconsensus/dapps/..." matched no packages
[test]              warning: "./trueconsensus/db/..." matched no packages
[test]              warning: "./trueconsensus/evm/..." matched no packages
[test]              2018/08/01 01:35:30 Unable to read config file. Error:open /etc/truechain/tunables_bft.yaml: no such file or directory 
[test]              --- FAIL: TestConfig (0.00s)
[test]              	assertions.go:256: 
[test]              			Error Trace:	config_test.go:32
[test]              			Error:      	Expected nil, but got: &os.PathError{Op:"open", Path:"/etc/truechain/tunables_bft.yaml", Err:0x2}
[test]              			Test:       	TestConfig
[test]              	assertions.go:256: 
[test]              			Error Trace:	config_test.go:33
[test]              			Error:      	Should not be: 0
[test]              			Test:       	TestConfig
[test]              FAIL
[test]              FAIL	trueconsensus/fastchain	0.024s
[test]              ?   	trueconsensus/fastchain/proto	[no test files]
[test]              ?   	trueconsensus/minerva	[no test files]
[test]              ?   	trueconsensus/client	[no test files]
[test]              ?   	trueconsensus/common	[no test files]
[test]              ?   	trueconsensus/logging	[no test files]
[test]              ?   	trueconsensus/snailchain	[no test files]

while expected output should be: PASS

I've tested this locally, abstracting the logic away from the codebase and it works.

So there's something that has not caught my attention yet.

@hixichen
Copy link
Contributor

hixichen commented Aug 1, 2018

This is not a issue.

If you had worked with docker image before, the root path is the exported path.

in test.sh, please check:
export GOPATH=pwd:pwd/..

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