-
Notifications
You must be signed in to change notification settings - Fork 26
add azure CI, temporarily disable others #107
Conversation
Thanks for getting this started Matti |
By mistake I tried with Cython-3.0a6 which failed. That is worrisome Edit: add link Cython fail
|
The 9 azure builds of (linux64, linux32, macos) * (python3.7, 3.8, 3.9) are green. I have set the repo up to build weekly at 3:27am UTC every Sunday. as well as for PRs. @tylerjereddy please take a look before I add tokens for uploading. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty solid to me--I added one question inline.
I did three spot checks for new CI test suite results vs. the same jobs on Travis CI, and the skipped/xfailed/xpassed results look quite close, which is a good sign for i.e., matching deps/setups:
64-bit Linux Python 3.9
Old Travis
40928 passed, 2252 skipped, 101 xfailed, 8 xpassed, 40 warnings in 1198.41s (0:19:58) =
Azure
41046 passed, 2260 skipped, 101 xfailed, 8 xpassed, 40 warnings in 627.73s (0:10:27) =
32-bit linux Python 3.7
Old Travis
40911 passed, 2260 skipped, 113 xfailed, 5 xpassed, 28 warnings in 992.99s (0:16:32)
Azure
41039 passed, 2258 skipped, 114 xfailed, 4 xpassed, 40 warnings in 759.56s (0:12:39) =
MacOS Python 3.8
Old Travis
30150 passed, 2067 skipped, 75 xfailed, 6 xpassed, 28 warnings in 589.91s (0:09:49) =
Azure
30274 passed, 2068 skipped, 75 xfailed, 6 xpassed, 28 warnings in 240.53s (0:04:00) =
The total numbers of passing tests are less relevant because that'll vary with the master
branch commit more easily, but even those are close looking to me.
Not sure if @rgommers has any additional comments, but seems like we can move forward with the token setup now?
|
||
- task: UsePythonVersion@0 | ||
inputs: | ||
versionSpec: $(AZURE_PYTHON_VERSION) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When is this version of the UsePythonVersion
task used? It looks like we always set the one for MB_PYTHON_VERSION
below in any case?
I guess AZURE_PYTHON_VERSION
is something I don't understand yet--is it built-in to Azure or coming from multibuild?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not from multibuild. Let me try to delete those steps. It came from MacPython/numpy-wheels#99, I think the comment "There is a problem with the Azure linux builds: for some reason it is setting the python version in the host machine even though that is not needed. I have a fix for that." was relevant but I cannot recall what it means.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it was from a time where the default python is 2.7, so we need to set something, but could not set 3.9 because Azure did not have it yet?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is needed for macOSx
Looks great to me, thanks for working on this @mattip. |
The upload step is failing but I think it is because this is a branch in my repo. So how to proceed without burning too many credits? Put back appveyor and merge this with travis disabled, and then enable travis in another PR after we see the uploads succeed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put back appveyor and merge this with travis disabled, and then enable travis in another PR after we see the uploads succeed?
+1 from me on that idea; also, there may be one line accidentally deleted in the Travis file? I commented inline for you to double check.
Apart from that, I think you can self-merge with Appveyor reactivated.
@@ -6,7 +6,6 @@ env: | |||
- PLAT=x86_64 | |||
- NP_BUILD_DEP="numpy==1.16.5" | |||
- CYTHON_BUILD_DEP="Cython==0.29.18" | |||
- PYBIND11_BUILD_DEP="pybind11==2.4.3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is still used by a line that hasn't been deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks. I reverted this change and changed the NP_*
requirement use oldest-supported-numpy
instead, like on azure.
"only" the upload is failing, so I will merge this with the travis runs disabled. |
.travis.yml
andazure-posix.yml
based on the one in numpy-wheels