The install path value in the Pytest parser was "/ansys_inc/v{version}/CEI". The new libuserd fixture is using this option, and since in the ADO builds we are not passing this option this folder is searched for. For the reasons in point 2., the installation is not found, and so in the ADO builds we are looking at an install at "/ansys_inc/v{version}/CEI" that does not exist
Differently from the PyEnSight installation search, the LibUserd installation search function was not considering the case the Python interpreter is exactly the EnSight Python Interpreter, like in the case of the ADO builds. The ADO builds rely on this search case, so I am adding the same functionality to look for the installation via the enve module
Two issues: