Replies: 6 comments
-
Bumping this topic. |
Beta Was this translation helpful? Give feedback.
-
+1 This is a huge oversight on the part of the GitHub Actions team. This is pretty basic CI functionality that is missing. This should 100% be prioritized. |
Beta Was this translation helpful? Give feedback.
-
Response from Github engineering last month here: |
Beta Was this translation helpful? Give feedback.
-
Related discussion: #35363 |
Beta Was this translation helpful? Give feedback.
-
Potentially related documentation issue: github/docs#25041 |
Beta Was this translation helpful? Give feedback.
-
Before reopening the linked bugs and discussions, was this really fixed? |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Describe the bug
When opening the "run" page for an active job you can see:
Gray checkmarks and expandable sections for completed steps and all of their log lines.
Yellow loading animation on any active steps.
Circles for the future steps.
The log lines for the active steps will then start streaming in, but the prior lines for that step are not there, and there appears to be no way to see them until the step completes.
To Reproduce
Steps to reproduce the behavior:
Run an action
Visit the run page after a few seconds and try to find the log lines for the currently running step that occurred before you loaded the page.
Expected behavior
All of the log lines that were emit before I loaded the page should be visible, then new ones stream in afterwards.
This bug has been raised twice and closed without resolution in the repo: actions/runner#886 actions/runner#2131. Stefan Ruvceski (presumably a GitHub staff member) said to raise it here.
This issue has been a pain for me for a while. Whenever I have a step that runs far longer than expected, I cannot look at the log to see where it has reached. I can't determine whether it's near the finish line or stuck somewhere near the beginning.
If developer inconvenience is insufficient cause to fix this, then another way to look at it is cost. If I know a step is stuck near the beginning from the log, I will probably stop it rather than letting it run in the hope it is near completion. Imagine this unnecessary processing across many errant steps in multiple Actions from many projects and the resources add up.
This really needs to be prioritised and fixed.
Beta Was this translation helpful? Give feedback.
All reactions