about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2017-03-24 15:42:15 +0000
committerbors <bors@rust-lang.org>2017-03-24 15:42:15 +0000
commitf2036c7be4e783f459d1f9a712c5a7b3ef6679bd (patch)
tree53d4dc37292387f15376d5c56419460bda768559
parent366386c46dbe660947de21dfd04eace5486e2f00 (diff)
parent37fd1320bd3a61b51831ccd6f3a19c990a6b2b8d (diff)
downloadrust-f2036c7be4e783f459d1f9a712c5a7b3ef6679bd.tar.gz
rust-f2036c7be4e783f459d1f9a712c5a7b3ef6679bd.zip
Auto merge of #40769 - alexcrichton:osx-crash-logs, r=nikomatsakis
travis: See if OSX generates crash dumps

I know for a fact we've had sccache segfault on various platforms and we've also
historically had a lot of problems with the linker on OSX. Let's just poke
around in the crash log directory to see if anything exists. If in the future we
see a build we think segfaulted *and* there's contents here then we can add some
bits that actually print out the logs.
-rw-r--r--.travis.yml12
1 files changed, 12 insertions, 0 deletions
diff --git a/.travis.yml b/.travis.yml
index 178dbc3d50d..1faf860a300 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -153,9 +153,21 @@ after_failure:
       echo "#### Build failed; Disk usage after running script:";
       df -h;
       du . | sort -nr | head -n100
+
+  # One of these is the linux sccache log, one is the OSX sccache log. Instead
+  # of worrying about what system we are just cat both. One of these commands
+  # will fail but that's ok, they'll both get executed.
   - cat obj/tmp/sccache.log
   - cat /tmp/sccache.log
 
+  # Random attempt at debugging currently. Just poking around in here to see if
+  # anything shows up.
+  - ls $HOME/Library/Logs/DiagnosticReports/
+
+  # attempt to debug anything killed by the oom killer on linux, just to see if
+  # it happened
+  - dmesg | grep -i kill
+
 # Save tagged docker images we created and load them if they're available
 before_cache:
   - docker history -q rust-ci |