vim tests break terminal output

  • Done
  • quality assurance status badge
Details
4 participants
  • Clément Lassieur
  • Efraim Flashner
  • Ludovic Courtès
  • Royce Strange
Owner
unassigned
Submitted by
Clément Lassieur
Severity
normal

Debbugs page

C
C
Clément Lassieur wrote on 29 Oct 2018 07:46
(address . bug-guix@gnu.org)
87sh0ovmic.fsf@lassieur.org
Hi,

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

Toggle snippet (24 lines)
<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@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

Cheers,
Clément
L
L
Ludovic Courtès wrote on 3 Nov 2018 06:58
(address . 33193@debbugs.gnu.org)
87zhuqp8je.fsf@gnu.org
Hello,
Clément Lassieur <clement@lassieur.org> skribis:
Toggle quote (13 lines)
> <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@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’.
L
L
Ludovic Courtès wrote on 3 Nov 2018 06:58
control message for bug #33193
(address . control@debbugs.gnu.org)
87y3aap8j8.fsf@gnu.org
tags 33193 moreinfo
E
E
Efraim Flashner wrote on 12 Nov 2018 10:12
Re: bug#33193: vim tests break terminal output
(name . Ludovic Courtès)(address . ludo@gnu.org)
20181112181218.GC25910@macbook41
On Sat, Nov 03, 2018 at 02:58:29PM +0100, Ludovic Courtès wrote:
Toggle quote (24 lines)
> Hello,
>
> Clément Lassieur <clement@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@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@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
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAlvpwn0ACgkQQarn3Mo9
g1GQtxAApjur2ZwMG4X2t6xhliiZ43oNa/0y1X3xIj4x2yBQ2XTm7VTmrEt/kUbk
/UbxXX9N1CLRkjxV9r1LMTVw6LKUJktiGCLEE5zLBraECUSyZtGC6iT+Mgnm1gf7
m0gg2uVAlSFHO9GokuXxy3dyXJ1RNNaG02VHtNd2i1VBfm/Dz5bPBM9szd7tcFda
a8fm7muZSpVmM5eNsaPgzmX4rF/LczXT+ZUZo8RsQu95iQuQn5osquRtS256LfSN
jUwcuF9jnUOp7h+GE2CLZMCL8teHpyGIna0xzrEtwuyUv++Oe/krFKeWdA/g0ucg
tCctae9x7u0uLPnvEC+GludxQd5OOG5GRa2658KLjz2Nv0f1pqjShjFD50J/rC7w
SkGCX6XdmMunnQ09UJdgdcKNSGB4ExhQX6RWVJp1hjbCOTUWZSctkHKyQWi2XQjl
tFXQhpaNX9XEezJ4z6WRKnfxQnrnfx25w70/dVsjs94YZ9c5iFgYsxiRutby+Rbl
7fpuEajbBkt+rgRZd1vTzxemFG0rV/CicavuzAZrwQybe2oxinygXPk8QZ5TNCx/
8RAFmQcCT3a4Hv3dGIg0YUVOQJBnhrA58+RBSp3s3IGU8aB/q/uQPvZX4tXMem9f
jIxi18Zs8Jp15QJ3SuCDsIIiiLRwuQE4W6ctOJ2s8eZU57spghY=
=XsHG
-----END PGP SIGNATURE-----


R
R
Royce Strange wrote on 10 Jun 2020 21:05
vim tests break terminal output
(address . 33193-done@debbugs.gnu.org)
87d066tfgc.fsf@disroot.org
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:

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.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 33193@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 33193
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch