From dc67711b6f64c9ccc72a5c2e4c783cb9a8740768 Mon Sep 17 00:00:00 2001
From: Andrei Vagin <avagin@google.com>
Date: Mon, 3 Apr 2023 18:41:51 -0700
Subject: [PATCH] builkite: log fatal signals

It can be useful to investigate bugs.

PiperOrigin-RevId: 521620352
---
 .buildkite/hooks/post-command | 1 +
 .buildkite/hooks/pre-command  | 2 ++
 2 files changed, 3 insertions(+)

diff --git a/.buildkite/hooks/post-command b/.buildkite/hooks/post-command
index ec991c575..ab4f9690a 100644
--- a/.buildkite/hooks/post-command
+++ b/.buildkite/hooks/post-command
@@ -54,6 +54,7 @@ rm -rf "${profile_output}"
 # Clean the bazel cache, if there's failure.
 if test "${BUILDKITE_COMMAND_EXIT_STATUS}" -ne "0"; then
   set -x
+  dmesg -kT | tail -n 50
   # LINT.IfChange
   runtime="buildkite_runtime_${BUILDKITE_BRANCH}-${BUILDKITE_BUILD_ID}"
   runtime="$(echo "$runtime" | sed -r 's~[^-_a-z0-9]+~_~g')"
diff --git a/.buildkite/hooks/pre-command b/.buildkite/hooks/pre-command
index 2943b0382..1b939b32a 100644
--- a/.buildkite/hooks/pre-command
+++ b/.buildkite/hooks/pre-command
@@ -110,3 +110,5 @@ if test "${BUILDKITE_AGENT_META_DATA_QUEUE}" = "release"; then
   # Configure the Docker credential helper (to push images).
   gcloud auth configure-docker -q
 fi
+
+sudo sysctl -w kernel.print-fatal-signals=1