From 7c5e7cc28752a50abdb9ecaa3c60ace76828d8f4 Mon Sep 17 00:00:00 2001 From: Christopher Baines Date: Sat, 1 Apr 2023 10:52:54 +0100 Subject: Don't call (backtrace) in the build allocator It seems to cause the same memory issues as calling (backtrace) with the hooks. --- guix-build-coordinator/coordinator.scm | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'guix-build-coordinator/coordinator.scm') diff --git a/guix-build-coordinator/coordinator.scm b/guix-build-coordinator/coordinator.scm index 6d3fc1d..54380f3 100644 --- a/guix-build-coordinator/coordinator.scm +++ b/guix-build-coordinator/coordinator.scm @@ -915,7 +915,14 @@ (allocate-builds build-coordinator) (metric-increment success-counter-metric)) (lambda (key . args) - (backtrace))) + (simple-format + (current-error-port) + "error in build allocator thread: ~A ~A\n" + key + args) + ;; TODO This seems to cause memory issues + ;;(backtrace) + )) (datastore-optimize (build-coordinator-datastore build-coordinator))) #:unwind? #t)) -- cgit v1.2.3