From 07f0bf3a503ab9f4603f6fed610036a5f0d0cc62 Mon Sep 17 00:00:00 2001
From: Jose Diaz-Gonzalez <email@josediazgonzalez.com>
Date: Sun, 28 Jun 2020 16:05:15 -0400
Subject: [PATCH] tests: try to output oomkill information

This should help identify if a failure is caused by oomkill or just bad code.
---
 .circleci/config.yml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/.circleci/config.yml b/.circleci/config.yml
index 575051897..ad7a3262a 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -54,7 +54,7 @@ jobs:
     steps:
       - init-tests
       - run:
-          name: test docker deploys
+          name: run docker deploy tests
           shell: /bin/bash
           no_output_timeout: 20
           command: |
@@ -66,7 +66,7 @@ jobs:
     steps:
       - init-tests
       - run:
-          name: run pre-tests
+          name: run go tests
           command: |
             case $CIRCLE_NODE_INDEX  in
               0) sudo -E make -e lint-ci go-tests ci-go-coverage ;;
@@ -82,10 +82,15 @@ jobs:
     steps:
       - init-tests
       - run:
+          name: run bats tests
           command: |
             sudo -E make -e test-ci
           no_output_timeout: 60m
           shell: /bin/bash
+      - run:
+          name: output oomkills
+          command: cat /var/log/syslog
+          when: on_fail
       - store_artifacts:
           path: ./test-results
           destination: test-results