-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[service] CI situation #11414
Comments
I've also been unable to get boost/1.79.0: Patch Boost.SmartPtr to support a specific variant of PowerPC #11402 to pass in CI on Windows for several days, even though the file the patch applies to shouldn't even be built in CI since it is for PowerPC only. |
It's under investigation, the source is not clear yet, most errors come from Windows machine, but not specific error, like network or disk usage. Sorry for the delay. |
You are right, we have been experiencing some unexpected errors in some agents that could be caused by unresponsive windows machines when they are under a certain load. We have restarted the Jenkins instance behind CCI and some of the windows machines have been restarted as well. Some of the PRs above are already running and the rest will follow them. Thanks a lot for notifying the issue and we will keep an eye on those jobs during the week. |
#11322 is also affected |
also: Does it help that we continue referencing the unexpected failures here, or is it an information you already have easily ? EDIT: I guess https://github.com/conan-io/conan-center-index/pulls?q=is%3Aopen+is%3Apr+label%3A%22Unexpected+Error%22+-label%3Ainfrastructure+ gives a good enough overview |
@ericLemanissier we can filter them by the Github label Unexpected Error. |
Looks like I'm seeing an issue for a missing pre-built binary for |
@jwillikers we are no longer building runtime MT + shared option. |
Back on the rails. Closing this one, the problem was related to Windows machines. Kudo to @danimtb |
I still keep getting unexpected errors with different versions of gtk always on Windows, any idea why? |
@hesham-essam your case is more specific. Let's discuss in your PR. I gonna take a look. |
@uilianries of all the PRs listed in this issue, a single one could be successfully built. There seem to be something else causing trouble again. |
@ericLemanissier I saw some linux machines were restarted. Last error we had were Windows machines ... Now we just need Mac to complete the trip of aces |
@uilianries @SSE4 @jgsogo @danimtb
Is there a situation with the CI ? Several PR's keep failing unexpectedly since last Friday, for example:
I guess we should all stop to close/reopen PRs in order to trigger CI, because it seems to trigger itself? We are quite in the dark here, especially since the CI does not report "in progress" status, and the auto-trigger period seems to be unpredictable (several hours to several days).
The text was updated successfully, but these errors were encountered: