emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#24819: closed (Intermittent 00-repl-server.test fa


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24819: closed (Intermittent 00-repl-server.test failure in 2.0.13)
Date: Fri, 04 Nov 2016 21:51:02 +0000

Your message dated Fri, 04 Nov 2016 22:50:11 +0100
with message-id <address@hidden>
and subject line Re: bug#24819: Intermittent 00-repl-server.test failure in 
2.0.13
has caused the debbugs.gnu.org bug report #24769,
regarding Intermittent 00-repl-server.test failure in 2.0.13
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24769: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24769
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Intermittent 00-repl-server.test failure in 2.0.13 Date: Sat, 29 Oct 2016 12:41:15 -0500
I noticed that 00-repl-server.test had failed on some of the debian
buildds like this:

  Running 00-initial-env.test
  Running 00-repl-server.test
  FAIL: 00-repl-server.test: repl-server: simple expression - arguments: 
(expected-value "scheme@(repl-server)> $1 = 42\n" actual-value "$1 = 42\n")

After suspecting some kind of race, it turns out that I can reproduce
the failure locally (eventually) like this:

  cd test-suite
  while GUILE_LOAD_PATH=. \
    ./guile-test tests/00-initial-env.test tests/00-repl-server.test
  do
    :
  done

I don't know what's causing the trouble yet, but I augmented
read-until-prompt to print every line it reads to stderr, and nothing
appeared amiss there, at least.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



--- End Message ---
--- Begin Message --- Subject: Re: bug#24819: Intermittent 00-repl-server.test failure in 2.0.13 Date: Fri, 04 Nov 2016 22:50:11 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
Hello!

Rob Browning <address@hidden> skribis:

> I noticed that 00-repl-server.test had failed on some of the debian
> buildds like this:
>
>   Running 00-initial-env.test
>   Running 00-repl-server.test
>   FAIL: 00-repl-server.test: repl-server: simple expression - arguments: 
> (expected-value "scheme@(repl-server)> $1 = 42\n" actual-value "$1 = 42\n")

The reason is that ‘repl-reader’ in boot-9.scm goes like this:

  (lambda* (prompt #:optional (reader (fluid-ref current-reader)))
    (if (not (char-ready?))
        (begin
          (display (if (string? prompt) prompt (prompt)))
          (set-port-column! (current-output-port) 0)))
    (force-output)
    (run-hook before-read-hook)
    ((or reader read) (current-input-port)))

Thus, if there’s already data available on the current input port, it
does not print the prompt.

That situation can arise in 00-repl-server.test if we write “(+ 40 2)”
too quickly.

Fixed in 2fbde7f02adb8c6585e9baf6e293ee49cd23d4c4.

Thanks!

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]