Replies: 2 comments
-
|
Hi there @yeputons and welcome to our community! Thank you for the feedback! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
It seems that this behavior was reverted at some point. Thank you! Here is a screenshot from three months ago, the Here is a screenshot from today, the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
In the fall of 2021, if you had a job which timed out, you was able to understand that by going on workflow's Summary page, scrolling down to "Annotations" and seeing text like
The job running on runner ..... has exceeded the maximum execution time of 3 minutes..Nowadays the comment lacks any details about the timeout and only says
The operation was canceled.without specifying the exact reason. The only way to guess (not know for sure) is to check job's running time and compare it with workflow's configuration.That's very confusing, especially for people who are just getting started with GitHub Actions. You have to both know about that quirk and be able to look up the timeout somewhere in the settings or the docs.
Would be nice if we can have that behavior back.
Beta Was this translation helpful? Give feedback.
All reactions