Adjust CI timeouts,resilient across branch names and stabilize long-running jobs#10983
Adjust CI timeouts,resilient across branch names and stabilize long-running jobs#10983morningstarxcdcode wants to merge 5 commits intodlang:masterfrom
Conversation
…w-hee ci: restore Alpine timeout budget in Main
|
Thanks for your pull request and interest in making D better, @morningstarxcdcode! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please see CONTRIBUTING.md for more information. If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment. Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + phobos#10983" |
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
120 minutes sounds crazy too me. What is it doing in that time? |
|
Yes, 60 minutes is the current hard max that the CI's are using. If you need more, it's time to investigate why and fix that instead. |
same |
|
anyone please approve this workflow |





this pr fixes a set of CI stability issues in the Main workflow
i have increase the timeout for Alpine and now it is in 60 same for macos also now 120 and kept job timeout expression as timeout 40 and also added DMDfallback logic in freebsd-vm job..