From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>,
"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Test failure - why?
Date: Fri, 26 Apr 2019 13:32:28 +0200 [thread overview]
Message-ID: <CAPFanBH+G9X=-R9mcpPeh6RAcQib79tq1na7c50kxtk=EfjtYA@mail.gmail.com> (raw)
In-Reply-To: <20190426100744.GA5136@prajna.paris.inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
From the compiler distribution directory, going to
testsuite/
and running
make one DIR=tests/tools-toplevel
I observe various output (actually in the run I made I can see this failure
line as well). The test that fails in my case is find-artifacts/, so there
is a log directory
tests/tool-debugger/find-artifacts/_ocamltest/
In particular there is a file
cat
tests/tool-debugger/find-artifacts/_ocamltest/tests/tool-debugger/find-artifacts/debuggee/ocamlc.byte/debuggee.byte.output
which ends with
Debugger [version 4.10.0+dev0-2019-04-23] environment error:
The files /usr/local/lib/ocaml/stdlib.cmi
and
/home/gasche/Prog/ocaml/github-trunk/testsuite/tests/tool-debugger/find-artifacts/_ocamltest/tests/tool-debugger/find-artifacts/debuggee/ocamlc.byte/out/blah.cmi
make inconsistent assumptions over interface Stdlib
This seems to be a problem where the testsuite environment is not
sufficiently isolated from the outside world, and another OCaml install
somewhere breaks things.
On Fri, Apr 26, 2019 at 12:08 PM Sébastien Hinderer <
Sebastien.Hinderer@inria.fr> wrote:
> Did you try to run the command manually to see what happens?
> Sébastien.
>
[-- Attachment #2: Type: text/html, Size: 1822 bytes --]
next prev parent reply other threads:[~2019-04-26 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 9:48 Richard W.M. Jones
2019-04-26 10:07 ` Sébastien Hinderer
2019-04-26 11:32 ` Gabriel Scherer [this message]
2019-04-26 11:41 ` Richard W.M. Jones
2019-04-26 12:03 ` Nicolás Ojeda Bär
2019-05-13 12:54 ` Sébastien Hinderer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPFanBH+G9X=-R9mcpPeh6RAcQib79tq1na7c50kxtk=EfjtYA@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=Sebastien.Hinderer@inria.fr \
--cc=caml-list@inria.fr \
/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.
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 NNTP newsgroup(s).