From: Philip Tricca <flihp at twobit.us>
To: tpm2@lists.01.org
Subject: Re: [tpm2] no files in test/tpmclient/good
Date: Tue, 10 Oct 2017 10:34:06 -0700 [thread overview]
Message-ID: <1507656846.22198.6.camel@twobit.us> (raw)
In-Reply-To: CAK5YYfg3MdTmh-58zdpCRp1rJnB7oM4eMFocnMAuH3K+BR8xRA@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
Hi Jan,
On Tue, 2017-10-10 at 16:37 +0200, Jan Schimmack wrote:
> after the compilation of the tpm2.0-tss on linux, I had to do an
> additional
>
> make test/tpmclient/tpmclient.int
This is expected behavior. The build system will only build test cases:
1) when you attempt to run the test harness (make check)
2) you explicitly build the test case (make path/to/test/exec)
> Then I started the tpmclient with
>
> ./test/tpmclient/tpmclient.int
>
> and most of the testcases passed. Anyways, i would like to know, how
> to produce output on
>
> test\tpmclient\good
I don't understand what your question is. The directory you reference
was full of "known good" output from test runs. However they were
generated years ago and were no longer accurate / being maintaned.
Can you clarify your question?
Thanks,
Philip
next reply other threads:[~2017-10-10 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 17:34 Philip Tricca [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-10 14:37 [tpm2] no files in test/tpmclient/good Jan Schimmack
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=1507656846.22198.6.camel@twobit.us \
--to=tpm2@lists.01.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox