Action on self-hosted machine terminated with The job has exceeded the maximum execution time of 6h0m0s
#180907
-
Why are you starting this discussion?Bug What GitHub Actions topic or product is this about?Actions Runner Discussion DetailsAccording to https://docs.github.com/zh/actions/reference/limits, the action running on a self-hosted machine has a 5-day job execution time limit. The related action: https://github.com/Fenyutanchan/IHEP-Multiloop-test/actions/runs/19844295821 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
💬 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.
-
|
Okay, I solved it. ...
jobs:
<job-name>:
runs-on: self-hosted
timeout-minutes: 7200 # for 5 days
... |
Beta Was this translation helpful? Give feedback.
-
|
Fabulous to see you come back after posting for the first time @Fenyutanchan and sharing your answer! Hopefully your effort will help others in the community ❤️ |
Beta Was this translation helpful? Give feedback.
Okay, I solved it.
According to https://docs.github.com/zh/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idtimeout-minutes, I can set