chore: use real exit codes for Postgres tests in CI (mozilla-services#1944)

Author: chenba

.circleci/config.yml

@@ -955,8 +955,6 @@ workflows:
               only: master
       - deploy-spanner-python-utils:
           requires:
-            - mysql-e2e-tests
-            - postgres-e2e-tests
             - spanner-e2e-tests
           filters:
             tags:

Makefile

@@ -110,7 +110,7 @@ docker_run_postgres_e2e_tests:
 	exit_code=$$?;
 	docker cp postgres-e2e-tests:/postgres_integration_results.xml ${POSTGRES_INT_JUNIT_XML};
 	docker cp postgres-e2e-tests:/postgres_no_jwk_integration_results.xml ${POSTGRES_NO_JWK_INT_JUNIT_XML};
-	exit 0;
+	exit $$exit_code;
 
 .ONESHELL:
 docker_run_spanner_e2e_tests:
@@ -172,7 +172,7 @@ postgres_test_with_coverage:
 	cargo llvm-cov --summary-only --json --output-path ${POSTGRES_COVERAGE_JSON} \
 		nextest --workspace --no-default-features --features=syncstorage-db/postgres --features=tokenserver-db/postgres --features=py_verifier --profile ${TEST_PROFILE}; exit_code=$$?
 	mv target/nextest/${TEST_PROFILE}/junit.xml ${POSTGRES_UNIT_JUNIT_XML}
-	exit 0
+	exit $$exit_code
 
 .ONESHELL:
 run_token_server_integration_tests: