You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fail fast in tests if avalancheGo executable isn't an absolute path
Currently when running ginkgo tests with --avalanchego flag with a relative path,
the tests fail when trying to ascertain the rpcvm plugin path, because they execute the binary
without an absolute path, and the binary path is evaluated from a wrong location.
In order to make the underlying issue clear, I added a check that fails the test
and warns that an absolute path must be used.
Signed-off-by: Yacov Manevich <[email protected]>
./bin/ginkgo -v ./tests/e2e -- --avalanchego-path=$PWD/build/avalanchego# Note that the path given for --avalanchego-path must be an absolute and not a relative path.
12
12
```
13
13
14
14
See [`tests.e2e.sh`](../../scripts/tests.e2e.sh) for an example.
0 commit comments