* bug#33193: vim tests break terminal output
@ 2018-10-29 14:46 Clément Lassieur
2018-11-03 13:58 ` Ludovic Courtès
2020-06-11 4:05 ` Royce Strange
0 siblings, 2 replies; 4+ messages in thread
From: Clément Lassieur @ 2018-10-29 14:46 UTC (permalink / raw)
To: 33193
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@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
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#33193: vim tests break terminal output
2018-10-29 14:46 bug#33193: vim tests break terminal output Clément Lassieur
@ 2018-11-03 13:58 ` Ludovic Courtès
2018-11-12 18:12 ` Efraim Flashner
2020-06-11 4:05 ` Royce Strange
1 sibling, 1 reply; 4+ messages in thread
From: Ludovic Courtès @ 2018-11-03 13:58 UTC (permalink / raw)
To: Clément Lassieur, ng0; +Cc: 33193
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’.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#33193: vim tests break terminal output
2018-11-03 13:58 ` Ludovic Courtès
@ 2018-11-12 18:12 ` Efraim Flashner
0 siblings, 0 replies; 4+ messages in thread
From: Efraim Flashner @ 2018-11-12 18:12 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 33193, Clément Lassieur, ng0
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On Sat, Nov 03, 2018 at 02:58:29PM +0100, Ludovic Courtès wrote:
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#33193: vim tests break terminal output
2018-10-29 14:46 bug#33193: vim tests break terminal output Clément Lassieur
2018-11-03 13:58 ` Ludovic Courtès
@ 2020-06-11 4:05 ` Royce Strange
1 sibling, 0 replies; 4+ messages in thread
From: Royce Strange @ 2020-06-11 4:05 UTC (permalink / raw)
To: 33193-done
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-06-11 4:06 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-10-29 14:46 bug#33193: vim tests break terminal output Clément Lassieur
2018-11-03 13:58 ` Ludovic Courtès
2018-11-12 18:12 ` Efraim Flashner
2020-06-11 4:05 ` Royce Strange
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.