The exit code from a bash script is the exit code of the last command. When I added Prisma, I used the last command to spin down the DB, so the test exit codes in Travis didn't represent the exit code from the test. I updated the scripts to store the exit code in a variable and use that code to exit the script.
Demo can now be run with:
start - ./bin/demo
stop - ./bin/demo stop
Screenshots or logs (if appropriate)
Questions:
Have you connected this PR to the issue it resolves? None
Does the documentation need an update? No
Does this add new dependencies? No
Have you added unit or functional tests for this PR? No
What does this PR do?
Do you have any concerns with this PR? No
How can the reviewer verify this PR?
Run demo or tests.
Any background context you want to provide?
The exit code from a bash script is the exit code of the last command. When I added Prisma, I used the last command to spin down the DB, so the test exit codes in Travis didn't represent the exit code from the test. I updated the scripts to store the exit code in a variable and use that code to exit the script.
Demo can now be run with:
./bin/demo./bin/demo stopScreenshots or logs (if appropriate)
Questions: