Conversation
|
I asked about this in the weekly meeting yesterday! There was mention that we keep Appveyor around because it tests conda, although I don't think anyone is enthusiastic about the frequent hangs. A lot of the discussion went over my head though as I'm still new to the whole Python ecosystem. |
I did port the conda test as well and now it looks like there must be some architectural difference (or running these tests now when we weren't before) because there are two minor 3d plot image comparison changes. |
a937204 to
8eaedaf
Compare
|
Not sure why the codecov/patch is reporting 0% diff, clicking into it does show the lines are being hit/missed same as before as expected. Looking at the timings, all CI jobs finished in 23 minutes, versus ~33 minutes (or more) on the previous azure/appveyor versions. |
This branch has not been deployed
2 participants
PR summary
The appveyor and azure jobs frequently have issues and take much longer to run. When doing some quick googling it looks like GitHub Actions uses the same underlying infrastructure but may get more resources per each CI job. This is an attempt to consolidate our CI into one common language so we don't have to know what the configuration formats for multiple CI providers is either.
Since Windows had some bespoke things in it I made this a separate workflow file so we don't overwhelm the existing tests yaml with conditions of
if windows...AI Disclosure
I had AI do the conversion of the configuration files from appveyor/azure into GitHub Actions and read through the output before PRing. I am not fluent in powershell, but it all looks reasonable.