Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
Hi, since roughly 3 months, our pipelines have started to randomly time out after 360 minutes/6 hours (where they normally take less than 10min). Restarting the workflow generally fixes the issue, and other parallel workflows of the same type (matrix for different versions of Python) have worked perfectly fine, so I don't think that the issue is with our code.
Also the test pipeline doesn't seem to be in the middle of anything very specific when it gets stuck. Without knowing if it's just do to the sequence or if there is really a causality, but it seems to get stuck (at different positions) during "killing" tests, making sure that a backup stays in a consistent state even if getting killed (by signal 15). This said, I don't really know how this could relate.
Repo is https://github.com/rdiff-backup/rdiff-backup/ and the pipeline failing is generally in
.github/workflows/test_linux.yml.Beta Was this translation helpful? Give feedback.
All reactions