Ludovic Courtès writes: Hello, > skribis: > >> Ludovic Courtès writes: [..] >>> I see several possible things to do: >>> >>> 1. Disable GC warnings altogether in Guix by setting ‘GC_warn_proc’. >>> >>> 2. Make sure guix-daemon discards stderr from agents such as ‘guix >>> authenticate’. >>> >>> 3. Figure out why those “Repeated allocation” messages are so frequent >>> on i586-gnu and Do Something About It™. [..] > Yeah, let’s start with (1), maybe with the patch below (untested)? > > (2) and (3) would be nice, but it goes with increasing difficulty. So...find two patches attached. A tested version of (untested) which was very helpful but did not compile. I should have tested with #if 1, and use #:tests? #f with guix right away... ;) Anyway, using this patch 0001 it seems that suppressing the warnings works, I no longer get --8<---------------cut here---------------start------------->8--- "GC Warning: Repeated allocation of very large block (appr. size 112 KiB):\n\tMay lead to memory leak and poor performance\n" --8<---------------cut here---------------end--------------->8--- but still get --8<---------------cut here---------------start------------->8--- unexpected build daemon error: stoi --8<---------------cut here---------------end--------------->8--- and the copy (and offload) still fails. Then I tried resetting LC_ALL >> How about >> >> 0. Unsetting LC_ALL on the Hurd >> >> would that work? > > I’m not sure, but if it does, it’s only “by chance”. (option 0.) anyway in a followup patch. Adding this patch 0003 (patch 0002 was just the guix package update), also the "stoi" warning is gone, and offloading works. So it seems that we have a workaround that "works by chance", WDYT? Greetings, Janneke