TST: Do not create symbolic link named gfortran. #15574
Conversation
|
@charris looks like this worked, do you want to remove the WIP? |
|
Heh, how about that, looks like gfortran comes preinstalled. Let me check that something else didn't change, from the comment gfortran was only needed for running the f2py tests, which I assume would be otherwise skipped. |
|
The comment needs updating, like "up to Feb 2020 the image did not include gfortran..." |
|
@mattip I'll put this in in a bit if you don't. |
|
Actually, let me comment the change first. |
The gfortran link is preinstalled since Feb 13, 2020 and attempting to create the link causes an error to be raised.
294bf34 to
62716e9
Compare
|
Merging even though travis did not finish, since the code in question is only active on azure. Thanks @charris. Do you know if azure does a merge-based run, or do we now have to rebase pull requests in order to get this in? |
|
@mattip I have had mixed results with just restarting failed tests, but close/reopen is pretty reliable, if more resource heavy. |
Apparently
gfortranhas been preinstalled for azure-pipeline Mac testing since February 13, 2020, so do not try to link our fortran version to the same name as it causes an error.