Hi,
Yes, you're right, the problems are due to the selftest environment
failing to start up. In this case, you could just reproduce the same
problem with:
SELFTEST_TESTENV=s4member:local make testenv
There may be some package dependencies you're missing in order to get
selftest to run correctly. In a earlier message it looked like you were
missing the python DNS package (python-dnspython on ubuntu). It looks
like you were still getting dns update errors on this latest test.
The other thing you could try is using ./configure.developer (instead of
./configure --enable-selftest), and rebuilding. This is how most
developers run selftest - I'm not sure how well tested the
--enable-selftest dependencies are on their own.
Cheers,
Tim
On 7/04/19 9:36 AM, Manfred via samba wrote:> In the hope for some help, I would like some hint on how to diagnose
> the following single subunit:
>
> samba3.blackbox.smbclient_machine_auth.plain
>
> In particular the single test
>
> samba3.blackbox.smbclient_machine_auth.plain
> (s4member:local)(s4member:local)
>
> Results attached, run is from git at 'origin/v4-10-stable'
> Thanks in advance
>
> (This is because in my full selftest almost all failures are from this
> error: "unable to set up environment")
>
> On 4/1/19 10:55 PM, Andrew Bartlett wrote:
>>
>> We would need to see the errors to diagnose further.
>>
>> Andrew Bartlett
>>
>