public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Rahul Kumar <rahulk@mvista.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] bzip2: Add test suite for bzip2
Date: Mon, 27 Apr 2020 16:09:55 +0100	[thread overview]
Message-ID: <e4d2de1d300677bf61ec737d8847dd7dea967840.camel@linuxfoundation.org> (raw)
In-Reply-To: <1587667187-14130-1-git-send-email-rahulk@mvista.com>

On Fri, 2020-04-24 at 00:09 +0530, Rahul Kumar wrote:
> Source: git://sourceware.org/git/bzip2-tests.git
> Type: Enhancement
> Description:
> bzip2 now has a test suite available at
> git://sourceware.org/git/bzip2-tests.git.
> 
> This is a collection of "interesting" .bz2 files that can be used to
> test bzip2 works correctly. They come from different projects.
> 
> Some files are deliberately bad, and are use to see how bzip2 handles
> corrupt files. They are explicitly not intended to decompress
> correctly,
> but to catch errors in bzip2 trying to deal with deliberately bad
> data.
> All such files have a name ending in .bz2.bad.
> 
> All non-bad files end in bz2. And should come with a .md5 file for
> the original input file. The .md5 file is used to check that bzip2
> could correctly decompress the file. The original (non-compressed)
> files are deliberately not checked in.
> 
> It will by default test with the command 'bzip2', running under
> valgrind (if installed on the system).
> 
> For each .bz2 file found it is decompressed, recompressed and
> decompressed again. Once with the default bzip2 settings and
> once in --small (-s) mode.
> 
> For each .bz2.bad file decompression is tried twice also. In
> default mode and small mode. The bzip2 binary is expected to
> return either 1 or 2 as exit status. Any other exit code is
> interpreted as failure.

I did try running this on the autobuilder. There are a few issues.

https://autobuilder.yoctoproject.org/typhoon/#/builders/62/builds/1816
step1b: ERROR: bzip2-1.0.8-r0 do_package_qa: QA Issue: /usr/lib/bzip2/ptest/bzip2-tests/.git/hooks/fsmonitor-watchman.sample contained in package bzip2-ptest requires /usr/bin/perl, but no providers found in RDEPENDS_bzip2-ptest? [file-rdeps]
step1b: ERROR: bzip2-1.0.8-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.

also, the new license (GPLv3) causes problems:

https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/1814

Cheers,

Richard




  reply	other threads:[~2020-04-27 15:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 18:39 [PATCH v2] bzip2: Add test suite for bzip2 Rahul Kumar
2020-04-27 15:09 ` Richard Purdie [this message]
2020-04-27 16:25   ` [OE-core] " Rahul Kumar
2020-04-27 16:30     ` Alexander Kanavin
2020-04-27 18:16       ` Richard Purdie
2020-04-27 18:54         ` Rahul Kumar
2020-04-27 19:39           ` Alexander Kanavin
2020-05-01  1:24             ` Randy MacLeod
2020-05-06 11:17               ` Rahul Kumar
     [not found]               ` <160C6C52084AA802.10857@lists.openembedded.org>
2020-05-12  4:58                 ` Rahul Kumar
2020-05-12 23:22                   ` Randy MacLeod
2020-05-13 14:28                     ` Trevor Gamblin
2020-05-13 18:28                       ` Rahul Kumar
2020-05-17 19:17               ` Rahul Kumar
2020-05-17 19:48                 ` Peter Kjellerstedt
2020-05-19 11:58                   ` Rahul Kumar
2020-05-19 16:29                     ` Peter Kjellerstedt
2020-05-19 17:14                       ` Rahul Kumar
2020-05-19 21:45                       ` Randy MacLeod
2020-05-19 22:10                         ` Khem Raj
2020-05-20  0:06                         ` Peter Kjellerstedt
2020-05-20 20:56                           ` Randy MacLeod
2020-05-25  6:12                             ` Rahul Kumar
2020-05-26 17:08                             ` Paul Barker
2020-05-12  6:53 ` Peter Kjellerstedt
2020-05-17 23:54   ` Khem Raj

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=e4d2de1d300677bf61ec737d8847dd7dea967840.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rahulk@mvista.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