how to run intgcheck?

[Chris Kowalczyk]

Hello All,

I have been trying to run sssd intgcheck, but to not success. Could you 
help me with it?

Generally, I've been performing the following steps:

autoreconf -if

./configure --disable-cifs-idmap-plugin --without-samba \
             --without-nfsv4-idmapd-plugin --without-secrets \
             --without-kcm --enable-intgcheck-reqs --with-os=suse

make intgcheck

...And getting this error:

configure: error: source directory already configured; run "make distclean"
there first

Of course, /make distclean/ destroys all the targets, so this is not a 
solution.


I tried to follow the example in /./contrib/fedora/bashrc_sssd/ and 
build the tests in a separate directory, but also without success:

autoreconf -if
cd x86_64

../configure --disable-cifs-idmap-plugin --without-samba \
             --without-nfsv4-idmapd-plugin --without-secrets \
             --without-kcm --enable-intgcheck-reqs --with-os=suse

make intgcheck

Running /make intgcheck/ from /x86_64/ directory complains about missing 
/cifsidmap/, so clearly there is some problem with configuration.


Could you advise me what steps I should take to build and run the 
integration tests?

Regards,
Chris

[Jakub Hrozek]

>  On 22 May 2018, at 10:24, Chris Kowalczyk <ckowalczyk(a)suse.com&gt;
> wrote:
>  
>  Hello All,
>  
>  I have been trying to run sssd intgcheck, but to not success. Could you help me with it?
>  Generally, I've been performing the following steps:
>  
>  autoreconf -if
>  ./configure --disable-cifs-idmap-plugin --without-samba \
>              --without-nfsv4-idmapd-plugin --without-secrets \
>              --without-kcm --enable-intgcheck-reqs --with-os=suse
>  
>  make intgcheck
>  
>  ...And getting this error:
>  
>  configure: error: source directory already configured; run "make distclean"
> there first 
Yes, the integration check configures sssd as well with some special overriden paths and
defaults. I don’t know if the intgcheck can be taught to respect the main project
configuration.

>  Of course, make distclean destroys all the targets, so this is not a
> solution.
>  
>  I tried to follow the example in ./contrib/fedora/bashrc_sssd and build the tests in a
> separate directory, but also without success: 
>  autoreconf -if
>  cd x86_64
>  
>  ../configure --disable-cifs-idmap-plugin --without-samba \
>              --without-nfsv4-idmapd-plugin --without-secrets \
>              --without-kcm --enable-intgcheck-reqs --with-os=suse
>  
>  make intgcheck
>  Running make intgcheck from x86_64 directory complains about missing cifsidmap, so
> clearly there is some problem with configuration. 
So if you want to run intgcheck with a non-default configure set you can run:

make intgcheck-run INTGCHECK_CONFIGURE_FLAGS="--disable-cifs-idmap-plugin
--without-samba (…etc)”

Does it help?

>  
>  
>  Could you advise me what steps I should take to build and run the integration tests?
>  Regards,
>  Chris
>  
>  
>  _______________________________________________
>  sssd-devel mailing list -- sssd-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to sssd-devel-leave(a)lists.fedorahosted.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...

[Chris Kowalczyk]

On 05/22/2018 10:56 AM, Jakub Hrozek wrote:
> > On 22 May 2018, at 10:24, Chris Kowalczyk
> <ckowalczyk(a)suse.com&gt; wrote:
> >
> > Hello All,
> >
> > I have been trying to run sssd intgcheck, but to not success. Could you help me with
> it?
> > Generally, I've been performing the following steps:
> >
> > autoreconf -if
> > ./configure --disable-cifs-idmap-plugin --without-samba \
> >              --without-nfsv4-idmapd-plugin --without-secrets \
> >              --without-kcm --enable-intgcheck-reqs --with-os=suse
> >
> > make intgcheck
> >
> > ...And getting this error:
> >
> > configure: error: source directory already configured; run "make distclean"
> there first
>  Yes, the integration check configures sssd as well with some special overriden paths and
> defaults. I don’t know if the intgcheck can be taught to respect the main project
> configuration.
>
> > Of course, make distclean destroys all the targets, so this is not a solution.
> >
> > I tried to follow the example in ./contrib/fedora/bashrc_sssd and build the tests in
> a separate directory, but also without success:
> > autoreconf -if
> > cd x86_64
> >
> > ../configure --disable-cifs-idmap-plugin --without-samba \
> >              --without-nfsv4-idmapd-plugin --without-secrets \
> >              --without-kcm --enable-intgcheck-reqs --with-os=suse
> >
> > make intgcheck
> > Running make intgcheck from x86_64 directory complains about missing cifsidmap, so
> clearly there is some problem with configuration.
>  So if you want to run intgcheck with a non-default configure set you can run:
>
>  make intgcheck-run INTGCHECK_CONFIGURE_FLAGS="--disable-cifs-idmap-plugin
> --without-samba (…etc)”
>
>  Does it help? 
Thanks, this helped indeed!

Is is possible to run one specific test? For example, after seeing that 
one of them failed, to run it again with some debug mode  (-d)?


Regards,
Chris

> >
> > Could you advise me what steps I should take to build and run the integration tests?
> > Regards,
> > Chris
> >
> >
> > _______________________________________________
> > sssd-devel mailing list -- sssd-devel(a)lists.fedorahosted.org
> > To unsubscribe send an email to sssd-devel-leave(a)lists.fedorahosted.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>

[Pavel Březina]

On 05/22/2018 11:35 AM, Chris Kowalczyk wrote:
>  On 05/22/2018 10:56 AM, Jakub Hrozek wrote:
> >> On 22 May 2018, at 10:24, Chris Kowalczyk <ckowalczyk(a)suse.com&gt; wrote:
> >>
> >> Hello All,
> >>
> >> I have been trying to run sssd intgcheck, but to not success. Could 
> >> you help me with it?
> >> Generally, I've been performing the following steps:
> >>
> >> autoreconf -if
> >> ./configure --disable-cifs-idmap-plugin --without-samba \
> >>              --without-nfsv4-idmapd-plugin --without-secrets \
> >>              --without-kcm --enable-intgcheck-reqs --with-os=suse
> >>
> >> make intgcheck
> >>
> >> ...And getting this error:
> >>
> >> configure: error: source directory already configured; run "make 
> >> distclean" there first
> > Yes, the integration check configures sssd as well with some special 
> > overriden paths and defaults. I don’t know if the intgcheck can be 
> > taught to respect the main project configuration.
> >
> >> Of course, make distclean destroys all the targets, so this is not a 
> >> solution.
> >>
> >> I tried to follow the example in ./contrib/fedora/bashrc_sssd and 
> >> build the tests in a separate directory, but also without success:
> >> autoreconf -if
> >> cd x86_64
> >>
> >> ../configure --disable-cifs-idmap-plugin --without-samba \
> >>              --without-nfsv4-idmapd-plugin --without-secrets \
> >>              --without-kcm --enable-intgcheck-reqs --with-os=suse
> >>
> >> make intgcheck
> >> Running make intgcheck from x86_64 directory complains about missing 
> >> cifsidmap, so clearly there is some problem with configuration.
> > So if you want to run intgcheck with a non-default configure set you 
> > can run:
> >
> > make intgcheck-run 
> > INTGCHECK_CONFIGURE_FLAGS="--disable-cifs-idmap-plugin --without-samba 
> > (…etc)”
> >
> > Does it help?
>  
>  Thanks, this helped indeed!
>  
>  Is is possible to run one specific test? For example, after seeing that 
>  one of them failed, to run it again with some debug mode  (-d)? 
You can run specific test like this:
https://github.com/pbrezina/sssd-dev-utils/blob/master/build-utils.sh#L101

However, attaching a debug level (and debugging tests in general) is 
problematic since sssd configuration is currently part of the test 
itself, so a modification of the test is needed.

I usually try to setup the same test case on a local sssd instance and 
then test it manually.