-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GCC installation fails on Azure Pipelines #15832
Comments
An example of verbose log:
|
I think the gcc package is called |
I think the test runs without gcc installation, can 0880f73e5f8343b3006fa2adb6d9bb09b3df8b55 be a workaround? As far as I had inspected the issue, I think there is a conflict of
But if I try to install
|
gcc-4.8.5 is old. It looks like related issue(s)(?) are currently being discussed on gitter: EDIT: I don't we think we should give up on having a C-compiler for at least some test environments. |
I think it was after |
I think gcc has to be built manually because it cannot be built on CI (it takes too long). I guess someone built it manually and uploaded it. You would have to ask on the conda-forge gitter for details. |
From the log in https://dev.azure.com/SymPy/SymPy/_build/results?buildId=1224,
It can imply that either gcc installed with
|
From one of my trials in https://dev.azure.com/SymPy/SymPy/_build/results?buildId=1235 GCC may had already been shipped with agent, so there may have not been any need to install gcc from the conda-forge from the first.
Possibly, there can be two ways to fix this issue. First way would be using the gcc shipped with azure, so the sympy's compilation utilities would use Other way would be making sympy's compilation utilities to make use of
|
Is @bjodah's suggestion about library code or just test code? |
My comment was regarding the |
Okay, so @sylee957 got a good answer on gitter: Jonathan J. Helmus:
We should install
those changes need to be made to: |
So this is related to this issue microsoft/azure-pipelines-tasks#8504. We should set $CC on Azure manually. |
I'd go with the first one. |
I also think we should go with the first one, in case that wasn't clear. |
Even for the first one, I think that environment variable should be manually set to the binaries like
I have a plan for fixing this in #15833 like adding environment variable manually |
yes, you can use |
You have to set the environment variables in the same script that the tests are run in. Unlike Travis, environment variables are not shared across scripts in Azure. See how the Sage environment variables work (they work around the same conda activate problem). |
I think manually setting environment variable to the compiler binaries are causing some issues. For example, looking up for
Though it is somewhat getting solved after installing And using
I think that there can be more complicated things going on the system while installing compiler package, or activating conda environment with compilers, and it may have to touch other environment variables or PATH variable. One of the newer posts in the thread |
When setting $CC and $FC to conda compilers we should also set:
if we have activated a conda environment the |
Anyway, I think workaround with using apt-get package installer goes fine. I think it may get more complicated to use I think it would be a better idea to open another matrix which would exclusively test compilers installed with conda, while the default optional dependency test would remain same to test the compilers installed directly with Right now, I have made a patch in #15857, which may solve current problems we are facing at least. |
I'd appreciate if you could give your opinion on Azure Pipelines in general https://groups.google.com/forum/#!msg/sympy/jyYrYz8ys9o/OrVSL4NeAQAJ. |
Azure pipelines was removed. #15998 |
I think azure had also started to fail on installing gcc, and it had gotten worse than #15671 as no optional dependency tests are getting run right now.
It had started failing after this commit
https://dev.azure.com/SymPy/SymPy/_build/results?buildId=1091
As long as my findings, I think I could reproduce the failing while installing gcc with anaconda in my local Windows Subsystem for Linux (ubuntu), but I may post some experiment PRs to see what really happens with verbose logs,
as this line suggests
The text was updated successfully, but these errors were encountered: