From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "qiutt@fujitsu.com" <qiutt@fujitsu.com>,
openembedded-core@lists.openembedded.org
Cc: fnstml-fujitsuten@fujitsu.com
Subject: Re: [OE-core] [meta-oe][PATCH V1] lz4: Add ptest support
Date: Tue, 04 Apr 2023 15:17:14 +0100 [thread overview]
Message-ID: <b0fb4536b693be4e8f1e564a8d6d8ee9031c9ec9.camel@linuxfoundation.org> (raw)
In-Reply-To: <1680602399-5469-1-git-send-email-qiutt@fujitsu.com>
On Tue, 2023-04-04 at 17:59 +0800, qiutt@fujitsu.com wrote:
> From: Qiu Tingting <qiutt@fujitsu.com>
>
> Add a ptest for lz4.
> - It is taking around 25 min to execute so added it to PTEST_SLOW.
> - It contains two case: test_frame, test_fuzzer.
> - Below is the run log:
> START: ptest-runner
> 2023-04-04T08:28
> BEGIN: /usr/lib/lz4/ptest
> Starting lz4frame tester (64-bits, 1.9.4)
> Seed = 485
> Basic tests completed
> All tests completed
> PASS: lz4/test_frame
> Starting LZ4 fuzzer (64-bits, v1.9.4)
> Seed = 7154
> Overflow tests : 64 bits mode : no overflow
> All unit tests completed successfully compressionLevel=9
> Overflow tests : 64 bits mode : no overflow
> All unit tests completed successfully compressionLevel=10
> generating low buffer at address 0x1000
> 65536 / 65536 - all tests completed successfully
> compression ratio: 54.326%
> HC compression ratio: 51.129%
> ratio with dict: 34.335%
> PASS: lz4/test_fuzzer
> DURATION: 1518
> END: /usr/lib/lz4/ptest
> 2023-04-04T08:53
> STOP: ptest-runner
> TOTAL: 1 FAIL: 0
>
> Signed-off-by: Qiu Tingting <qiutt@fujitsu.com>
25 minutes seems slow, is that with KVM? How much of the time is in the
frame test and how much is in the fuzzer?
We should probably just run the frame tests and skip the fuzzing as
we're interested in integration testing, not random tests!
Cheers,
Richard
next prev parent reply other threads:[~2023-04-04 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 9:59 [meta-oe][PATCH V1] lz4: Add ptest support qiutt
2023-04-04 14:17 ` Richard Purdie [this message]
2023-04-06 1:55 ` [OE-core] " qiutt
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=b0fb4536b693be4e8f1e564a8d6d8ee9031c9ec9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=fnstml-fujitsuten@fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qiutt@fujitsu.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