From mboxrd@z Thu Jan 1 00:00:00 1970 From: rendaw <7e9wc56emjakcm@s.rendaw.me> Subject: bug#35379: Long lines in `guix` output are truncated at screen width Date: Wed, 24 Apr 2019 03:30:17 +0900 Message-ID: References: <42f3ade8-5d7c-9f9d-6d8d-886734b1ffa2@s.rendaw.me> <87ftq8j24c.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:32854) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJ0C8-0004T0-K1 for bug-guix@gnu.org; Tue, 23 Apr 2019 14:31:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hJ0C7-00027I-F1 for bug-guix@gnu.org; Tue, 23 Apr 2019 14:31:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:40801) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hJ0C6-00026T-Id for bug-guix@gnu.org; Tue, 23 Apr 2019 14:31:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hJ0C6-0006O6-6b for bug-guix@gnu.org; Tue, 23 Apr 2019 14:31:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87ftq8j24c.fsf@gnu.org> Content-Language: en-US List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 35379@debbugs.gnu.org On 4/23/19 10:13 PM, Ludovic Courtès wrote: > Hi rendaw, > > rendaw <7e9wc56emjakcm@s.rendaw.me> skribis: > >> I get logs like: >> >> /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/sbin/grub-install: >> error: >> /gnu/store/6zkimxsfyn0gdc7p4ikxlrhilpnpblsi-grub-efi-2.02/lib/grub/i386-pc/modinfo.sh >> doesn't exist. Please spe. > Hmm weird. Can you tell exactly how to reproduce this issue? > I don’t see what could be truncating these lines. > > Thanks in advance, > Ludo’. I thought this was normal, but I tried reproducing it in a vm. It appears that the truncation starts after qemu starts the image in ``` guix system disk-image my-config.scm -v 10 ``` and the truncation continues thereafter.  I tested by doing: ``` (display (iota 200)) (display "\n") (force-output) (display (iota 200)) ``` This prints before and after the qemu step of the build.  Before the qemu process it looks like lines are wrapped properly.  After the qemu process the lines are truncated.  And lines are truncated before+after for subsequent builds until I reset the vm. I can send the Vagrantfile and provisioning script + what I did manually to do the build if you'd like. The main issue is the build fails, I turn -v 10 on to see the verbose logs, but then the logs I need (during/post qemu) are truncated so I'm still not getting the important information.