tests: try to output oomkill information

This should help identify if a failure is caused by oomkill or just bad code.
This commit is contained in:
Jose Diaz-Gonzalez committed 2020-06-28 16:05:15 -04:00
1 parent bcfa530056
commit 07f0bf3a50
1 file changed
+7 -2
+7 -2
View File
@@ -54,7 +54,7 @@ jobs:
steps: steps:
- init-tests - init-tests
- run: - run:
name: test docker deploys name: run docker deploy tests
shell: /bin/bash shell: /bin/bash
no_output_timeout: 20 no_output_timeout: 20
command: | command: |
@@ -66,7 +66,7 @@ jobs:
steps: steps:
- init-tests - init-tests
- run: - run:
name: run pre-tests name: run go tests
command: | command: |
case $CIRCLE_NODE_INDEX in case $CIRCLE_NODE_INDEX in
0) sudo -E make -e lint-ci go-tests ci-go-coverage ;; 0) sudo -E make -e lint-ci go-tests ci-go-coverage ;;
@@ -82,10 +82,15 @@ jobs:
steps: steps:
- init-tests - init-tests
- run: - run:
name: run bats tests
command: | command: |
sudo -E make -e test-ci sudo -E make -e test-ci
no_output_timeout: 60m no_output_timeout: 60m
shell: /bin/bash shell: /bin/bash
- run:
name: output oomkills
command: cat /var/log/syslog
when: on_fail
- store_artifacts: - store_artifacts:
path: ./test-results path: ./test-results
destination: test-results destination: test-results