With upgrading of dev environment to F38 and updating test containers to F38 I tried to fix all the tests.
Unfortunatelly, there is one issue, which I tracked to https://pagure.io/ipsilon/blob/acd44b0d7495364a9be01bca932731ad21c1d29d/f/ipsilon/providers/saml2/auth.py#_387 and it seems that this is randomly failing tests in F38. All other container tests are passing, only the F38 is failing now. The issue is hard to debug, because there isn't any error anywhere in the test logs and the python-lasso is just a wrapper over .so C library. I even tried to downgrade to same version as on F37, but it doesn't seem to work on F38.
Hopefully the issue will be fixed in newer versions of lasso library.
I'm thinking about downgrading the vagrant dev env to F37, where the tests are currently passing. What do you think?
I can also remove F38 from containertest Makefile target, so the tests are passing for now.
With upgrading of dev environment to F38 and updating test containers to F38 I tried to fix all the tests.
Unfortunatelly, there is one issue, which I tracked to https://pagure.io/ipsilon/blob/acd44b0d7495364a9be01bca932731ad21c1d29d/f/ipsilon/providers/saml2/auth.py#_387 and it seems that this is randomly failing tests in F38. All other container tests are passing, only the F38 is failing now. The issue is hard to debug, because there isn't any error anywhere in the test logs and the python-lasso is just a wrapper over
.soC library. I even tried to downgrade to same version as on F37, but it doesn't seem to work on F38.Hopefully the issue will be fixed in newer versions of lasso library.
I'm thinking about downgrading the vagrant dev env to F37, where the tests are currently passing. What do you think?
I can also remove F38 from
containertestMakefile target, so the tests are passing for now.