diff options
author | Christopher Baines <mail@cbaines.net> | 2023-04-01 10:52:54 +0100 |
---|---|---|
committer | Christopher Baines <mail@cbaines.net> | 2023-04-01 10:52:54 +0100 |
commit | 7c5e7cc28752a50abdb9ecaa3c60ace76828d8f4 (patch) | |
tree | b8e609da80a15fbc5b7da7902b00c5e522d10d7c | |
parent | 7a9998348836b4be9456c98ee95f25f587ada77f (diff) | |
download | build-coordinator-7c5e7cc28752a50abdb9ecaa3c60ace76828d8f4.tar build-coordinator-7c5e7cc28752a50abdb9ecaa3c60ace76828d8f4.tar.gz |
Don't call (backtrace) in the build allocator
It seems to cause the same memory issues as calling (backtrace) with the
hooks.
-rw-r--r-- | guix-build-coordinator/coordinator.scm | 9 |
1 files changed, 8 insertions, 1 deletions
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)) |