Skip to content
This repository has been archived by the owner on Jan 27, 2019. It is now read-only.

Dependency issue when testing with Gradle while native Go tests succeed #24

Open
tglaeser opened this issue Mar 4, 2017 · 2 comments
Open

Comments

@tglaeser
Copy link

tglaeser commented Mar 4, 2017

I believe there is a dependency issue when building with Gradle that otherwise does not exist.

To reproduce ...

$ mkdir -p $GOPATH/src/github.com/tendermint
$ git clone https://github.com/tendermint/tendermint $GOPATH/src/github.com/tendermint/tendermint
$ cd $GOPATH/src/github.com/tendermint/tendermint
$ git checkout develop
$ git pull
$ glide install
$ go install ./cmd/tendermint
$ go test ./mempool
ok      github.com/tendermint/tendermint/mempool        0.218s
$ gradle --no-daemon build
...
:baseTest FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':baseTest'.
> At least one test failed (see log).

File $GOPATH/src/github.com/tendermint/build.gradle is

plugins {
  id "org.echocat.golang" version "0.1.15"
}
group 'github.com/tendermint/tendermint'
golang {
    toolchain {
        goroot = '/cygdrive/c/opt/go'
    }
    build {
        useTemporaryGopath = false
    }
}

Reviewing file build/testing/test.log show that previously successful test github.com/tendermint/tendermint/mempool now fails with a compile error ...

# github.com/tendermint/tendermint/proxy
src/github.com/tendermint/tendermint/proxy/app_conn.go:143: cannot use reqQuery (type types.RequestQuery) as type []byte in argument to app.appConn.QuerySync
src/github.com/tendermint/tendermint/proxy/app_conn.go:143: not enough arguments to return
have (types.Result)
want (types.ResponseQuery, error)
src/github.com/tendermint/tendermint/proxy/client.go:76: undefined: types.NewBaseApplication
FAIL github.com/tendermint/tendermint/mempool [build failed]

There were changes recently done to the code with respect to types.ResponseQuery. What I don't understand is why this only fails when building with Gradle.

Please advise. Thanks.

@tglaeser
Copy link
Author

Do you have an update for me? Is the plugin still actively maintained/developed?

@blaubaer
Copy link
Member

Hey @tglaeser: Currently I does not explicitly work on this issue but I still maintain/develop this project. I still focused on older issues at first. 😄

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

No branches or pull requests

2 participants