unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>, ng0 <ng0@infotropique.org>
Cc: 33193@debbugs.gnu.org
Subject: bug#33193: vim tests break terminal output
Date: Sat, 03 Nov 2018 14:58:29 +0100	[thread overview]
Message-ID: <87zhuqp8je.fsf@gnu.org> (raw)
In-Reply-To: <87sh0ovmic.fsf@lassieur.org> ("Clément Lassieur"'s message of "Mon, 29 Oct 2018 15:46:35 +0100")

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’.

  reply	other threads:[~2018-11-03 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 14:46 bug#33193: vim tests break terminal output Clément Lassieur
2018-11-03 13:58 ` Ludovic Courtès [this message]
2018-11-12 18:12   ` Efraim Flashner
2020-06-11  4:05 ` Royce Strange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhuqp8je.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33193@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    --cc=ng0@infotropique.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).