Hello,
I have recently started experiencing problems when running tests for my project on Azure Pipelines with a Windows instance (vmImage: 'windows-2019'). Digging a little bit deeper (see this conversation https://developercommunity.visualstudio.com/content/problem/1102472/azure-pipeline-error-with-windows-vm.html?childToView=1119179#comment-1119179) we realised that the problem originated when we install numpy 1.19.0 instead of numpy 1.8.5 - I can see that numpy 1.19.0 was put on PyPI on June 20 and this is around the time when our tests started to fail. Forcing the environment to install numpy 1.8.5 as in previously successful builds seem to solve the problem.
I just wanted to report this as I assume this is something others may have started observing (but it is quite hard to pin-point that numpy is the issue... or at least looks like it is).
Looking forward to hearing from you,
and happy to do any change to my azure pipeline setup if that can help troubleshooting the problem.
Error message:
This build works fine with numpy 1.18.5: https://dev.azure.com/matteoravasi/PyLops/_build/results?buildId=46&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e
A build on the same commit with numpy 1.19.0 fails: https://dev.azure.com/matteoravasi/PyLops/_build/results?buildId=43&view=results
The error is very cryptic, what I explained above is more relevant I think. Here it is anyways:
2020-07-06T13:56:01.6879900Z Windows fatal exception: Current thread 0xaccess violation00001798
2020-07-06T13:56:01.6880280Z
2020-07-06T13:56:01.6880589Z (most recent call first):
2020-07-06T13:56:01.6880973Z File "<__array_function__ internals>", line 6 in vdot
2020-07-06T13:56:05.3412520Z ##[debug]Exit code: -1073741819
Hello,
I have recently started experiencing problems when running tests for my project on Azure Pipelines with a Windows instance (
vmImage: 'windows-2019'). Digging a little bit deeper (see this conversation https://developercommunity.visualstudio.com/content/problem/1102472/azure-pipeline-error-with-windows-vm.html?childToView=1119179#comment-1119179) we realised that the problem originated when we installnumpy 1.19.0instead ofnumpy 1.8.5- I can see thatnumpy 1.19.0was put on PyPI on June 20 and this is around the time when our tests started to fail. Forcing the environment to installnumpy 1.8.5as in previously successful builds seem to solve the problem.I just wanted to report this as I assume this is something others may have started observing (but it is quite hard to pin-point that numpy is the issue... or at least looks like it is).
Looking forward to hearing from you,
and happy to do any change to my azure pipeline setup if that can help troubleshooting the problem.
Error message:
This build works fine with numpy 1.18.5: https://dev.azure.com/matteoravasi/PyLops/_build/results?buildId=46&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e
A build on the same commit with numpy 1.19.0 fails: https://dev.azure.com/matteoravasi/PyLops/_build/results?buildId=43&view=results
The error is very cryptic, what I explained above is more relevant I think. Here it is anyways: