From: Catonano <catonano@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: make check
Date: Sat, 2 Mar 2019 15:58:48 +0100 [thread overview]
Message-ID: <CAJ98PDwMPPCHKd7Msba59w_Rmi9n4WT2mv5cZe+wZdAqfAzVNQ@mail.gmail.com> (raw)
In-Reply-To: <20190301105157.GB1806@spikycactus-com.attlocal.net>
Il giorno ven 1 mar 2019 alle ore 11:52 Mike Gran <spk121@yahoo.com> ha
scritto:
> On Mon, Feb 25, 2019 at 09:30:46AM +0100, Catonano wrote:
> > I added a test to the test-suite/tests/texinfo.serialize.test file,
> >
> > like this
> >
> > (assert-serialize '(defcodeindex (% (entry "op")))
> > "@defcodeindex opi
> > ")
>
> I tried it and it works for me. My guess is that you didn't put your test
> inside of the "with-test-prefix" block. All tests need to be inside of
> a "with-text-prefix" block.
>
It worked for me too, I had just forgot to save the file after I had edited
it. So I was running the previous version :-/
> >
> > please note that the texinfo string is wrong
> >
> > I run make check expecting to see a failed test but they all pass
> >
> > Is my new test being run ? It seems it isn't
> >
> > Also, how do I run the texinfo tests only (rather than all of them) ?
>
>
> >
> > I tried
> >
> > ../meta/guile -L ./ guile-test tests/texinfo*.test
> >
> > this line returns the prompt but no output and I can't find any log file
>
> To run just the texinfo tests, from the test-suite/tests directory,
> you can run the following command
>
> ../../check-guile texinfo*test
>
> Your output will be in the check-guile.log file
>
>
Than you Mike, I appreciate this
I had found that already, i don't know how
prev parent reply other threads:[~2019-03-02 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 8:30 make check Catonano
2019-03-01 10:51 ` Mike Gran
2019-03-02 14:58 ` Catonano [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ98PDwMPPCHKd7Msba59w_Rmi9n4WT2mv5cZe+wZdAqfAzVNQ@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=spk121@yahoo.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).