From: Vincent Jacques <vincent@vincent-jacques.net>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] bisect-report and including directories
Date: Fri, 11 Mar 2016 08:53:00 +0100 [thread overview]
Message-ID: <CAEnGa7BiB9G17mqOP0H6oKt=CtPLkNAPx3JdKK236cDa3Z1FQg@mail.gmail.com> (raw)
In-Reply-To: <m2h9gd31v2.fsf@charm-ecran.irisa.fr>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
I think I've had exactly the same problem.
IIRC it was specific to html reports: other formats worked.
My work-around was to run bisect-report in a dedicated, temporary,
directory where I copied all the sources.
2016-03-11 8:33 GMT+01:00 Alan Schmitt <alan.schmitt@polytechnique.org>:
> Hello,
>
> After moving things around in a project, I'm having trouble generating
> bisect reports. This works (in the "interp" directory):
>
> % bisect-report -I _build -html ../report ../bisect*.out
>
> but this does not work (in the directory above):
>
> % bisect-report -I interp/_build -html report bisect*.out
> *** system error: src/extract/JsInterpreterBisect.ml: No such file or
> directory
>
> The file is there though:
>
> % ls interp/_build/src/extract/JsInterpreterBisect.ml
> interp/_build/src/extract/JsInterpreterBisect.ml
>
> Have other bisect users encountered this issue?
>
> Thanks a lot,
>
> Alan
>
> --
> Openpgp Key ID : 040D0A3B4ED2E5C7
> Monthly Athmospheric CO₂ (2016-02, Mauna Loa Obs.): 404.02
>
--
Vincent Jacques
http://vincent-jacques.net
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème"
Devise Shadock
[-- Attachment #2: Type: text/html, Size: 1827 bytes --]
next prev parent reply other threads:[~2016-03-11 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 7:33 Alan Schmitt
2016-03-11 7:53 ` Vincent Jacques [this message]
2016-03-11 16:27 ` Anton Bachin
2016-03-14 7:25 ` Alan Schmitt
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='CAEnGa7BiB9G17mqOP0H6oKt=CtPLkNAPx3JdKK236cDa3Z1FQg@mail.gmail.com' \
--to=vincent@vincent-jacques.net \
--cc=alan.schmitt@polytechnique.org \
--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).