WIP, CI: add newer msvc to Azure CI#3399
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #3399 +/- ##
========================================
Coverage 94.06% 94.06%
========================================
Files 176 176
Lines 23282 23282
Branches 3302 3302
========================================
Hits 21901 21901
Misses 1335 1335
Partials 46 46 Continue to review full report at Codecov.
|
|
ah, still using an older msvc ( |
17289d7 to
2d7425b
Compare
|
Yup, it's picking up the augment error. How very interesting, we could try to lower the optimization to 01 for windows? Although that's kinda annoying given it's probably a test that relies on too accurate a float precision rather than an actual issue... |
|
@IAlibay there we go--I got MSVC 2019 running for one Azure matrix entry and the two failures you mention are reproduced. The raw log is here, and I've pasted the two tracebacks below the fold since the logs can purge out after 10 days. Details |
|
I'll leave the "WIP" in the title for now since I'm not sure if you'll want to just merge the fix in to here when ready or xfail/merge/remove the xfail, etc. |
Thanks for working on this @tylerjereddy ! @richardjgowers - thoughts on just xfailing the test? I think you mentioned it probably wasn't a problem? It is using StoR stuff, which I think @hmacdope mentioned was quite flaky? |
|
@IAlibay Yeah it's not fantastic obviously but not a show stopper, I don't think we actually use these functions often. If we're dropping precision it might be possible to drop to O2 and see if that fixes it for now? |
|
Hello @tylerjereddy! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2022-01-21 20:31:58 UTC |
8c60aaf to
5f21527
Compare
|
@richardjgowers I've pushed in a change to drop to |
|
@tylerjereddy does |
|
No idea, I'm testing by CI so we will see soon |
|
It looks like the answer is "no" to optimization level drop helping; also, results are slightly more confusing because of the h5py release causing a new windows failure I think. |
|
For the use of StoR in #3360 I just had to drop the number of decimals I was matching to. :( |
|
@tylerjereddy - sorry I just did a commit to see what happened if we dropped to O1 (just to rule out an optimisation being the cause here). |
|
No dice - I guess there's a deeper issue here. |
* try to capture the test error described in MDAnalysisgh-3248 by using the newest possible Windows base image/compiler toolset to run a matrix entry * I have not tried overriding with `imageName` in a matrix entry like this before, but it seems it is documented: https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-multiplatform?view=azure-devops
* try lowering the compiler optimization level on Windows to deal with precision loss with msvc 2019
This reverts commit 6e2b1d1.
* bump to new Azure windows image more broadly * `xfail` `test_augment` on Windows per MDAnalysisgh-3248
6e2b1d1 to
78f1786
Compare
|
@IAlibay Ok, I pushed in the changes to apply the Windows image bump more broadly and temporarily xfail the problematic test on Windows until the issue is resolved. I guess we'll see if the CI is happy. I probably could have scoped the |
IAlibay
left a comment
There was a problem hiding this comment.
Assuming CI returns green - lgtm! Thanks so much @tylerjereddy !
try to capture the test error described in
[pre-release 1.1.0] test_augment failure on windows #3248 by using the newest possible Windows
base image/compiler toolset to run a matrix
entry
I have not tried overriding with
imageNamein a matrix entry like this before, but it seems
it is documented:
https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-multiplatform?view=azure-devops
PR Checklist