Issue with the Python path in the recent builds

[lekshmideepu]

We have some issue with the wrong python path. Since yesterday evening, our builds are using the python from the /opt which is 2.7.13. We tried to debug the build. It seems like you are executing the /etc/profile.d/pyenv.sh. For our builds, we were using the system python. (2.7.6)
Problematic build is here.
Due to the wrong python path, it cannot find the mpi4py module.

[meatballhat]

@lekshmideepu Have you been able to work around this with an explicitly defined PYTHONAPATH?

[lekshmideepu]

@meatballhat yes, By explicitly defining the path works.

[jougs]

@meatballhat: @lekshmideepu and I tried to export PATH=/usr/bin/:$PATH right before installing Python modules via apt-get and that seems to circumvent the problem. To our knowledge, PYTHONPATH is not set explicitly, but just implicitly by the sys.path in the python used.

We believe that the root cause for the problem is that etc/profile.d/pyenv.sh puts the bin directories of the Python installations in /opt/python/ before the system path /usr/bin instead of after. etc/profile.d/pyenv.sh apparently was not executed in the old images (cf. old, new).

[jougs]

@meatballhat: do you expect this to be resolved quickly? If not, we probably should apply our workaround to our setup and restart the failing jobs. Thanks!

[lekshmideepu]

@meatballhat : We are waiting for your response. Could you please let us know about the status of the issue.

[lekshmideepu]

@jougs @meatballhat I have contacted the support via email and received an update about the issue.

[lekshmideepu]

Travis team is working on this issue and they confirmed that it is a bug. One suggested workaround is to use "language: minimal" in the .travis.yml. This will route the builds to the Connie stack, which is the stack in which Python builds ran before the update. After the update, Python builds are now running in the Sugilite stack and it appears to be overwriting the PYTHONPATH.

[Lyoness]

Thanks for sharing the workaround @lekshmideepu and for submitting this issue.

We've been able to push up changes to all image stacks using python. Currently they are available in group: edge, which you can specify in your .travis.yml to test if the path issues get fixed. Let us know if this works for you. We're working on promoting edge to group: stable soon.

[lekshmideepu]

@Lyoness Thanks for the update. I tried with the group option edge, unfortunately PythonLibs for version3 are not found as shown here.
On the other hand, if I use the deprecated option, it works fine.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues