Lukas Slebodnik wrote:
> On (02/12/15 13:14), Rob Crittenden wrote:
>> Is it still mandatory that tests pass the unit tests before acceptance?
> Unit test could be executed as part of "%check" phase in spec files.
> I recently added C-base unit tests there.
> I was not bale to run "make tests" there because many tests failed.
> If they require real IPA server for execution ( or lite server)
> then they are not unit test but integration tests.
> One solution would be to skip them or to usw cwrap + lite server.
> So it can be run also in mock/koji which has many restrictions.
It would represent quite a lot of work but it may be a good idea to
investigate. Ipsilon uses cwrap for its tests so some of the
configuration can be gleaned from that.
I would definitely be opposed to this as part of the freeipa.spec in the
git tree. In Fedora it might help find problems when rawhide becomes
Fedora.next so it would provide some value there.
> Also lint should be also part of "%check" phase and not part of
> ordinary build.
> BTW I could not see a lint in fedora build at all. So I'm not sure
> if it is executed with upstream spec file.
It isn't there because the expectation is that lint already passes as
part of the release process. I don't see the value on running lint on
I also want to keep the focus on the reviewer's responsibility to ensure
that patches do what they are supposed to and don't break things.
> If someone wants to comply that it would take long time to build rpms
> then you might take a look how long glibc is built.
> (half an hour on x86_64)
>> I've seen a number of cases over the past couple of months where a
>> change goes through then shortly afterward a patch to fix the tests.
>> IMHO this should be caught in advance.
>> Things slip through and goodness knows I've acked more than a few
>> patches without running the full suite. I just have a feeling it has
>> become more frequent lately.
>  https://cwrap.org/
Manage your subscription for the Freeipa-devel mailing list:
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code