Running a local test via docker-compose, I get exit code 137 instead of 1 when the tests fail. See below:
Running ANY failing tests via:
docker-compose up --exit-code-from pgtap --build pgtap;echo $?
I get:
Starting ccitest_pgtap_1 ... done
Attaching to ccitest_pgtap_1
pgtap_1 | Waiting for database...
pgtap_1 | 2020/02/01 01:43:55 Waiting for: tcp://postgres:5432
pgtap_1 | 2020/02/01 01:43:55 Connected to tcp://postgres:5432
pgtap_1 |
pgtap_1 | Running tests: /test/*.sql
... test output here ...
pgtap_1 | Failed tests: 9, 12-15
pgtap_1 | Parse errors: Bad plan. You planned 14 tests but ran 15.
pgtap_1 | Files=1, Tests=15, 47 wallclock secs ( 0.03 usr + 0.01 sys = 0.04 CPU)
pgtap_1 | Result: FAIL
Aborting on container exit...
Stopping ccitest_pgtap_1 ... done
137
Successful tests do correctly produce the correct exit code (0).
Running a local test via docker-compose, I get exit code 137 instead of 1 when the tests fail. See below:
Running ANY failing tests via:
docker-compose up --exit-code-from pgtap --build pgtap;echo $?I get:
Successful tests do correctly produce the correct exit code (0).