Hi Dirk,
On 09/19/2018 03:13 AM, Dirk Zimoch wrote:
> On 19.09.2018 10:01, Dirk Zimoch wrote:
>> Then I recognized that all the other tests in the Makefile have a line
>>
>> TESTS += ...
>>
>> but performstruct has not. Is this a bug?
Nope...
> Hmm.... when adding it to TESTS I get
>
> $make runtests
> [...]
> performstruct.t ......... skipped: (no reason given)
>
> What does this mean?
All our test programs have human-readable output, the Test Anything
Protocol (TAP) output was designed for that. If you run this program by
hand you get this output:
> tux% ./performstruct
> # void {anonymous}::buildMiss()
> # 1000 sample 18.938251 +- 3.830785 us
> # void {anonymous}::buildHit()
> # 1000 sample 16.096664 +- 1.622438 us
>
> Results
> =======
> Tests: 0
As you can see, it's doing some performance measurement, not functional
testing. That's why it isn't included in the list of tests that get run
by 'make runtests' and friends. There are a few other similar test
programs spread around the Base tree which are intended for manual
operation only and should not be added to TESTS.
- Andrew
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
- Replies:
- Re: Problem with performstruct test Michael Davidsaver
- References:
- Problem with performstruct test Dirk Zimoch
- Re: Problem with performstruct test Dirk Zimoch
- Navigate by Date:
- Prev:
Re: Problem with performstruct test Dirk Zimoch
- Next:
Re: Problem with performstruct test Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Problem with performstruct test Dirk Zimoch
- Next:
Re: Problem with performstruct test Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|