From: Richard Palethorpe <rpalethorpe@suse.de>
To: Xinkuan Yan <lucky33newman@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] Question about log format.
Date: Mon, 12 Dec 2022 14:36:55 +0000 [thread overview]
Message-ID: <87mt7su1dg.fsf@suse.de> (raw)
In-Reply-To: <CAFQkDyZABHU38_LTvsv1eP8PvK4rHprfZrL45CYqMvav1-O8_A@mail.gmail.com>
Hello,
Xinkuan Yan <lucky33newman@gmail.com> writes:
> Hello list,
>
> I'm trying to do a concise parsing of the LTP report.
>
> I don't have much experience and I'm not familiar with LTP, so I'm going to
> take #math as an example, for it is not complex.
>
> Run test command:
>
> ./ltp –f math –q
>
> I have three questions now, taking the one-line output result below as an
> example:
>
> float_iperb 1 TPASS: Test passed
This is a test using the old API, so not the best example.
>
> 1, It is clear that TPASS means it passed, but what is the number 1
> standing for.
I don't know to be honest. It was removed in the new test API.
>
> 2, Why this line showed up twice? ( PS: Between these two lines are many
> TINFO.)
Possibly because there are multiple iterations of the test. Possibly
some paramters are changed between iterations.
Only way to find out is to look for tst_resm calls in the source code.
>
> 3, Where to check those out put standards, taking yocto package test as a
> small comprehension, that standard was ( PASS|FAIL|SKIP): Test info. How is
> it like in LTP?
https://github.com/linux-test-project/ltp/wiki/C-Test-API#12-basic-test-interface
Note taht the new API output looks more like the following:
sh-5.2# ./bpf_prog07
tst_buffers.c:55: TINFO: Test is using guarded buffers
tst_taint.c:116: TCONF: Ignoring already set kernel warning taint
tst_test.c:1560: TINFO: Timeout per run is 0h 00m 30s
bpf_common.c:17: TINFO: Raising RLIMIT_MEMLOCK to 10485760
tst_capability.c:29: TINFO: Dropping CAP_SYS_ADMIN(21)
tst_capability.c:29: TINFO: Dropping CAP_BPF(39)
bpf_common.c:39: TCONF: Hint: check also /proc/sys/kernel/unprivileged_bpf_disabled
bpf_common.c:41: TCONF: bpf() requires CAP_SYS_ADMIN or CAP_BPF on this system: EPERM (1)
Summary:
passed 0
failed 0
broken 0
skipped 3
warnings 0
sh-5.2# ./bpf_prog01
tst_buffers.c:55: TINFO: Test is using guarded buffers
tst_test.c:1560: TINFO: Timeout per run is 0h 00m 30s
bpf_common.c:17: TINFO: Raising RLIMIT_MEMLOCK to 10485760
bpf_common.c:114: TPASS: Loaded program
bpf_prog01.c:95: TPASS: val = 1
...
So the format is like:
<file_name>:<line>: <ttype>: <message>
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-12 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 22:30 [LTP] Question about log format Xinkuan Yan
2022-12-12 9:10 ` Cyril Hrubis
2022-12-12 14:36 ` Richard Palethorpe [this message]
2022-12-13 11:53 ` Xinkuan Yan
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=87mt7su1dg.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
--cc=lucky33newman@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.