[Rpm-maint] rpm test suite
pmatilai at laiskiainen.org
Wed Feb 13 08:56:06 UTC 2013
On 02/13/2013 08:56 AM, Alexey Tourbin wrote:
> On Tue, Feb 12, 2013 at 06:38:19AM +0200, Panu Matilainen wrote:
>> NAK, something here causes severe breakage in rpmbuild (a pile of
>> segfault failures in the test-suite, and its not the above case of
>> self-undefining macro as that's not tested currently). For example:
>> [pmatilai at localhost rpm]$ ./rpmbuild -ts
>> *** glibc detected *** /home/pmatilai/repos/rpm/.libs/lt-rpmbuild:
>> free(): invalid next size (fast): 0x00000000006c4620 ***
>> Aborted (core dumped)
>> [pmatilai at localhost rpm]$
>> When submitting patches, please make sure "make check" completes
>> without errors. The test-suite is somewhat picky of how rpm is
>> ./configure'd so you'll want to get it working with a known-good
>> starting point (git master is expected to pass with zero errors at
>> all times, or somebody has screwed up) before hacking further. It's
>> a bit of a PITA as it takes so long to complete, but its also been a
>> life-saver on numerous occasions...
> I'm currently not able to set up a known-good starting point (on git
> master) - there are failures.
Right, its almost certainly some kind of setup issue then, there are no
expected failures at current git master. Typically its just a thing or
two that cause pretty much everything to fail. IIRC one common cause is
not specifying --prefix=<path> to rpm's ./configure script (that's an
ages old bug in the rpm makesystem rather than test-suite, but test
suite is the first place where people typically run into it)
> Is there a way to run tests individually
> and in kind of a verbose mode - i.e. with commands being run and
> actual/expected output?
In the tests/ directory you can run them one by one with "./rpmtests
<number>", add -v for verbose output.
The logs of failed cases are preserved in
tests/rpmtests.dir/<number>/rpmtests.log, those usually are sufficient
to reveal the problem(s).
- Panu -
More information about the Rpm-maint