Running tests produces an error
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 236
- PR merge metrics
- No merged PRs in 30d
Description
This occurs on OSX Sierra (10.12.4)
% ./bin/wasabi.sh start test
...
wasabi: building
unable to prepare context: unable to evaluate symlinks in context path: lstat //wasabi-default/modules/main/target/wasabi-main-1.0.20170418213834-development: no such file or directory
wasabi: starting
5cab474bc720951b46e0b37eafad236866074137f331130b8478918195d7e92f
chill'ax error: not started
usage: container.sh [options] [commands]
options:
-v | --verify [ true | false ] : verify installation configuration; default: false
-m | --migration [ true | false ] : refresh cassandra migration scripts; default: false
-s | --sleep [ sleep-time ] : sleep/wait time in seconds; default: 3
-h | --help : help message
commands:
start[:wasabi,cassandra,mysql,docker] : start all, wasabi, cassandra, mysql, docker
stop[:wasabi,cassandra,mysql,docker] : stop all, wasabi, cassandra, mysql, docker
console[:cassandra,mysql] : console all, cassandra, mysql
status : status
remove[:wasabi,cassandra,mysql]] : remove all, wasabi, cassandra, mysql
error: unable to start
...
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with ./bin/wasabi.sh and the container.sh usage shown in the report, then reproduce the test startup command on the reported environment. Trace the missing target path and container startup failure; done means the test command starts successfully without the reported context or “not started” errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java, shell
- Domain
- build-system, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100