GNU bug report logs - #33193
vim tests break terminal output

Previous Next

Package: guix;

Reported by: Clément Lassieur <clement <at> lassieur.org>

Date: Mon, 29 Oct 2018 14:47:02 UTC

Severity: normal

Tags: moreinfo

Done: Royce Strange <royball <at> disroot.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 33193 in the body.
You can then email your comments to 33193 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#33193; Package guix. (Mon, 29 Oct 2018 14:47:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Clément Lassieur <clement <at> lassieur.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Mon, 29 Oct 2018 14:47:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Clément Lassieur <clement <at> lassieur.org>
To: bug-guix <at> gnu.org
Subject: vim tests break terminal output
Date: Mon, 29 Oct 2018 15:46:35 +0100
Hi,

While build vim tests, the terminal gets weird and its output is broken.

--8<---------------cut here---------------start------------->8---
<ng0> [...] some build (no idea which one, I'm in a long series of
      builds) just broke the output in a way that I'm only getting
      gibberish for the renmaining tail of buildlogs. iirc vim builds
      (specifically: the testsuite) would do something similar to your
      open terminal.
      [15:22]
*** mbuf (~Shakthi <at> 45.251.33.79) has quit: Quit: Leaving  [15:24]
<ng0> "but what do I mean by gibberish?"
<ng0> well:
<ng0> ⎻▒▒⎽e ◆b┤☃┌d' ⎽┤cceeded ▒°├e⎼ 1↓3 ⎽ec⎺┼d⎽
<ng0>
      ├e⎽├/e┼±☃┼e/├e⎽├_⎻⎺⎺┌↓⎻≤::P⎺⎺┌E┴e┼├⎽Te⎽├::├e⎽├_c⎺┼┼ec├_⎺┼_⎽┤b⎽e─┤e┼├┌≤_⎼ec⎼e▒├ed
      PASSED [ 2▮%]
<ng0> etc
<roptat> oh yes, vim tests :/  [15:25]
<roptat> is that with guix build or guix package?  [15:26]
<ng0> build
<roptat> I haven't seen anything like that before and I'm not familia with UI
	 code  [15:27]
<ng0> wiht building vim you'd get no problems a while back. it would just
      continue building and only when builds finish make your terminal act
      funny
--8<---------------cut here---------------end--------------->8---

Cheers,
Clément




Information forwarded to bug-guix <at> gnu.org:
bug#33193; Package guix. (Sat, 03 Nov 2018 13:59:02 GMT) Full text and rfc822 format available.

Message #8 received at 33193 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Clément Lassieur <clement <at> lassieur.org>, ng0
 <ng0 <at> infotropique.org>
Cc: 33193 <at> debbugs.gnu.org
Subject: Re: bug#33193: vim tests break terminal output
Date: Sat, 03 Nov 2018 14:58:29 +0100
Hello,

Clément Lassieur <clement <at> lassieur.org> skribis:

> <ng0> [...] some build (no idea which one, I'm in a long series of
>       builds) just broke the output in a way that I'm only getting
>       gibberish for the renmaining tail of buildlogs. iirc vim builds
>       (specifically: the testsuite) would do something similar to your
>       open terminal.
>       [15:22]
> *** mbuf (~Shakthi <at> 45.251.33.79) has quit: Quit: Leaving  [15:24]
> <ng0> "but what do I mean by gibberish?"
> <ng0> well:
> <ng0> ⎻▒▒⎽e ◆b┤☃┌d' ⎽┤cceeded ▒°├e⎼ 1↓3 ⎽ec⎺┼d⎽
> <ng0>
>       ├e⎽├/e┼±☃┼e/├e⎽├_⎻⎺⎺┌↓⎻≤::P⎺⎺┌E┴e┼├⎽Te⎽├::├e⎽├_c⎺┼┼ec├_⎺┼_⎽┤b⎽e─┤e┼├┌≤_⎼ec⎼e▒├ed
>       PASSED [ 2▮%]

ng0, could you send the version of ‘guix-daemon’ and that of ‘guix’ as
well as the exact output you’re seeing?

TIA,
Ludo’.

Added tag(s) moreinfo. Request was from ludo <at> gnu.org (Ludovic Courtès) to control <at> debbugs.gnu.org. (Sat, 03 Nov 2018 13:59:03 GMT) Full text and rfc822 format available.

Information forwarded to bug-guix <at> gnu.org:
bug#33193; Package guix. (Mon, 12 Nov 2018 18:13:01 GMT) Full text and rfc822 format available.

Message #13 received at 33193 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 33193 <at> debbugs.gnu.org, ng0 <ng0 <at> infotropique.org>,
 Clément Lassieur <clement <at> lassieur.org>
Subject: Re: bug#33193: vim tests break terminal output
Date: Mon, 12 Nov 2018 20:12:18 +0200
[Message part 1 (text/plain, inline)]
On Sat, Nov 03, 2018 at 02:58:29PM +0100, Ludovic Courtès wrote:
> Hello,
> 
> Clément Lassieur <clement <at> lassieur.org> skribis:
> 
> > <ng0> [...] some build (no idea which one, I'm in a long series of
> >       builds) just broke the output in a way that I'm only getting
> >       gibberish for the renmaining tail of buildlogs. iirc vim builds
> >       (specifically: the testsuite) would do something similar to your
> >       open terminal.
> >       [15:22]
> > *** mbuf (~Shakthi <at> 45.251.33.79) has quit: Quit: Leaving  [15:24]
> > <ng0> "but what do I mean by gibberish?"
> > <ng0> well:
> > <ng0> ⎻▒▒⎽e ◆b┤☃┌d' ⎽┤cceeded ▒°├e⎼ 1↓3 ⎽ec⎺┼d⎽
> > <ng0>
> >       ├e⎽├/e┼±☃┼e/├e⎽├_⎻⎺⎺┌↓⎻≤::P⎺⎺┌E┴e┼├⎽Te⎽├::├e⎽├_c⎺┼┼ec├_⎺┼_⎽┤b⎽e─┤e┼├┌≤_⎼ec⎼e▒├ed
> >       PASSED [ 2▮%]
> 
> ng0, could you send the version of ‘guix-daemon’ and that of ‘guix’ as
> well as the exact output you’re seeing?
> 
> TIA,
> Ludo’.

I experimented a bit with updating our version on vim and the gibberish
went away. Unfortunately I was unsuccessful in upgrading it.


-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[signature.asc (application/pgp-signature, inline)]

Reply sent to Royce Strange <royball <at> disroot.org>:
You have taken responsibility. (Thu, 11 Jun 2020 04:06:01 GMT) Full text and rfc822 format available.

Notification sent to Clément Lassieur <clement <at> lassieur.org>:
bug acknowledged by developer. (Thu, 11 Jun 2020 04:06:01 GMT) Full text and rfc822 format available.

Message #18 received at 33193-done <at> debbugs.gnu.org (full text, mbox):

From: Royce Strange <royball <at> disroot.org>
To: 33193-done <at> debbugs.gnu.org
Subject: vim tests break terminal output
Date: Wed, 10 Jun 2020 23:05:23 -0500
Hello.

Efraim Flashner said that the garbled output while building
vim disappeared when he updated it.
It has been two years and both vim and vim-full have been
updated in guix since the last comment on this issue.

Checking cuirass, there is no garbled output:
https://ci.guix.gnu.org/log/dnj9wljcck9vdwgp7dwxk00qnnk1g3c5-vim-full-8.2.0411
https://ci.guix.gnu.org/log/yajzgb2zlkklg5l9cpnsimrsjzmvq5x2-vim-8.2.0411

Building locally,
My terminal survived and didn't notice any output getting garbled.
(i am using emacs-vterm)

-----
$ guix --version
guix (GNU Guix) 2971ed57345ee4e00058efeaf27c6a0790fdc9dd

$ guix build vim --no-substitutes
$ guix build vim-full --no-substitutes
-----

Going to go ahead and close out.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Thu, 09 Jul 2020 11:24:07 GMT) Full text and rfc822 format available.

This bug report was last modified 3 years and 292 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.