Open kloczek opened 1 year ago
Internally the test suite uses k5test which is where this exception is occurring. Unfortunately there are a lot of layers that can make it hard to capture this output from Popen redirection to the unittest stdout capturing.
If this was me I would
/usr/sbin/krb5kdc -n
interactively and see if it works, if it doesn't hopefully it gives you a clear errorbuild is performed in env which is cut off from access to the public network (pytest is executed with -m "not network")
AFAIK this requires the actual tests themselves to include a network
marker which this repo does not have.
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulescut off from access to the public network
(pytest is executed with-m "not network"
)I have issue with testing module on packaging and becaise almost all units are emmiting with the same errors I suppose that something is wrong with my testing procedure. I've been trying to have lookm on CI however I was unable to find necessary clues abot what I I'm doing wrongly. May I ask for some help/hints?
Here is pytest output:
Here is list of installed modules in build env