-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add onnx/1.8.1 #4810
add onnx/1.8.1 #4810
Conversation
Failure in build 1 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
I was surprised to not be able to reproduce those errors, until I tried to disable Ninja and fall back to Makefiles. Just have to figure out what happen with Makefiles. |
in-source build is broken for some generators
Failure in build 3 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
There are also random build failures due to concurrent access to several files. I've submitted a patch upstream onnx/onnx#3317 |
Failure in build 4 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
This issue with undefined references is not reproducible. |
Failure in build 5 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
So now Visual Studio 16 / MD / Release / Static is OK in build 5 (KO in 3 & 4), but I didn't change anything between build 3 & 5 to fix this issue. |
All green in build 6 (
|
And now it builds, well pretty sure there is something wrong in Visual Studio 16 agent. |
Failure in build 7 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
This unpredictable error in Visual Studio 16 agent is tedious. |
Failure in build 8 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
Failure in build 9 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
Failure in build 10 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
All green in build 11 (
|
Hi! Sorry for the delay. There are more than one Windows machines, all of them with VS 16. It looks like it fails for one of them, but not for the others, so it has to be something related to our installation. I would say it is this same issue: https://developercommunity.visualstudio.com/t/-dyn-tls-on-demand-init-and-tls-guard-related-weir/1010557 Q:
Answer:
Now, I need to have a look at how it translates to our infrastructure. |
Found it! Some machines are running |
Specify library name and version: onnx/1.8.1
conan-center hook activated.
closes #4728