Public Beta Feedback - Actions streaming logs with backscroll

[andrewakim]

Actions streaming logs with backscroll

We are starting to rollout a change to give you more log context for active jobs in Actions. Previously, refreshing or navigating away from a running job's logs meant losing that context. Now, as soon as you open the logs, you'll see the last 1,000 lines, making it simpler to stay updated on job progress and status.

How to give feedback

Over the next few weeks, we’ll be rolling this feature out to all Actions customers. If you see a new beta label near the top of the log window (see image below) this means the feature is active for your workflow. If you run into any issues or have any feedback, please comment below!

For bugs, please comment on this post and provide as much information as possible. This includes a basic explanation of the issue, how to replicate it, browser and version, and a picture or video if possible. Thank you!

⚠️	If you are using a self-hosted runner or a VPN, please ensure that your network access settings are up-to-date.

Updates

April 22, 2024

• We are preparing to move into GA this week and will be closing this thread. Thank you everyone for your feedback. If you experience any issues or have additional feedback to share, please create a new discussion.

February 26, 2024

• We will be making updates today starting around 12:00 UTC that may cause intermittent impacts to backscrolling. All other log behavior should remain the same.

February 22, 2024

• We are planning on rolling out some changes starting around 12:00 UTC on February 23 that may cause intermittent impacts to backscrolling throughout the day. All other log behavior should remain the same. (Postponed)
• We're aware of the issue where some log line numbers may be out of order.
• We've fixed the issue where logs would not be available and display an error message about retention settings.

February 13, 2024

• We're aware of an issue specific to the Safari browser where logs will not stream and only appear upon refreshing the browser. We've added an issue on our side and are investigating it. (Resolved as of April 22)
• We're also aware of the issue where the previous 1,000 lines of logs retrieved when a page is loaded all have the same timestamp. The team is looking into this as well. (Resolved as of Feb 19)
• If you are using a self-hosted runner and experiencing an issue where logs or job summaries fail to load, please ensure that your network access settings are updated.

[karthik-varma-hh]

loving it so far <3

[PatTheMav]

As mentioned in the OP:

We're aware of an issue specific to the Safari browser where logs will not stream and only appear upon refreshing the browser. We've added an issue on our side and are investigating it.

The issue seems to be known without a fix so far, so all we can do is wait..

[G-Titan]

probably an incorrect syntax in the yaml file

[tkgaurav]

no option left to re-run Github Actions for user interface ?

[adrianbastholm]

we see two steps that should be sequential running at the same time.
Impersonate service account and the subsequent deployment to Cloud Run were running at the same time, and hung

[kingtistel]

I'm on Mac M1 Pro Sonoma 14.4.1 and I have the same issue with Chrome also

[Rkrushanovskij]

On page reload or coming to job logs during the job execution, usage of "Show timestamps" feature displays all the previous logs at the timestamp of initial loading on page open. To get actual log line timestamp you have to wait for job to finish.
Would be great to have actual timestamps on logs initial load.

[malvads]

indeed

[andrewakim]

Thanks for sharing! I've created an issue and added this to our backlog.

[techabstraction]

I'd like this also.

[MCLifeLeader]

Thoughts on tying in GitHub Copilot to analyze logs? When I started adding actions I ran into challenges getting them to work. Having Copilot right there to look at logs would be awesome.

[Gui-FernandesBR]

Maybe in the future we could have a kind of report showing which jobs are consuming more runtime computing.

[trajan0x]

btw, swarmia does a great job at this.

E.g. here's what it looks likes for this repo

[a-dubaj]

Loving it so far :)

[stefanpantic-pdftools]

Hey, sounds like a useful feature! I currently have the issue where no logs for a job show up until it completes.

[andrewakim]

@stefanpantic-pdftools - If possible, would you be able to share a screenshot? Also, your browser and version would help our investigation!

[stefanpantic-pdftools]

Don't think a SS would really help, the job logs were printed when it failed. Currently for me logs have the old behavior (and the beta badge is gone). For browser I'm using Google Chrome Version 120.0.6099.234 (Official Build) (arm64) on macOS.

[shqear93]

The current step is "Executing the action" and it's not showing up between the list of the step

@andrewakim

[OJFord]

I have no logs for a job that has completed, maybe because a different job in the workflow is running (retried), will find out when it finishes I suppose..

[patchwork01]

This isn't showing the logs at all for me in our workflows now. I just see "Error:" in red any time I expand a step to try to see the logs.

In my web browser's console I can see a "Cross-Origin Request Blocked" error. If I click on the link for the network request that was refused, I see the logs that are failing to display. It seems to be failing to load the logs because the host name is different from the page I'm on.

Here's a workflow where I get that:

https://github.com/gchq/sleeper/actions/runs/7611249162/job/20726325480

This happened in Firefox. Here's what I see:

[jcave-relay]

I and many others in my organization also get this error. No - I am not using a proxy.

[andrewakim]

👋 @jcave-relay - Can you share a link to a run where you're seeing this error? You can use the Google Form to share the link.

[ekohl]

I see the same in https://github.com/theforeman/puppet-puppet/actions/runs/8174732159/job/22350216851?pr=908 where the logs are retrieved via XHR requests from productionresultssa15.blob.core.windows.net. I use uMatrix to block requests to third parties by default, which means this update breaks for me unless I allow those requests. I see https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github documents this, but I don't want to allow requests to the windows.net domain.

I don't see a way to opt out of this?

[jsoref]

You could pay for GHES, deploy, and use it until the version you're using is EOL.

[jsoref]

You can already do that. https://github.com/orgs/community/discussions/89879#discussioncomment-8695418

[kumaranvpl]

This is one thing which has been frustrating me for quite a while.
I don't have to worry about accidentally closing the tab anymore.
Thank you.

[mohamedtalhaouii]

guys help me for get the badges

[wilkinson4]

I've been noticing an issue viewing the actions while they're running. For some reason it won't let me see the output of the job's steps until the entire job is complete. I'm using Firefox and Chrome on MacOS Sonoma 14.2.1

[freakboy3742]

Seeing the same thing here. This was the first job where I was part of the beta. All self-hosted runners; if I load a job while it's running, I get the full backlog of log messages, but no ongoing scrolling. This is on Safari 17.1.2 on macOS 13.6.2.

[Spacetown]

we use GitHub hosted runners. In Firefox the log doesn't appear while the job is running and in Safari you need to refresh to have the log updated.

[ClausKlein]

I am missing lots of details in output of a job, too if I switch to row log?

#9 2090.3 + pushd /axcioma/build
#9 2090.3 + run-clang-tidy '-checks=-*,bugprone-*,-bugprone-reserved-identifier,hicpp-*,-hicpp-avoid-c-arrays,-hicpp-exception-baseclass,-hicpp-no-array-decay,-hicpp-braces-around-statements'
#9 2094.4 2713 warnings generated.
#9 2094.4 Suppressed 2713 warnings (2713 in non-user code).
#9 2094.4 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2094.4 2714 warnings generated.
#9 2094.4 Suppressed 2712 warnings (2712 in non-user code).
#9 2094.4 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2094.6 3090 warnings generated.
#9 2094.6 Suppressed 3083 warnings (3083 in non-user code).
#9 2094.6 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2094.8 3066 warnings generated.
#9 2094.8 Suppressed 3059 warnings (3059 in non-user code).
#9 2094.8 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2098.3 2735 warnings generated.
#9 2098.3 Suppressed 2733 warnings (2733 in non-user code).
#9 2098.3 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2098.7 2716 warnings generated.
#9 2098.7 Suppressed 2712 warnings (2712 in non-user code).
#9 2098.7 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2099.4 2689 warnings generated.
#9 2099.4 Suppressed 2689 warnings (2689 in non-user code).
#9 2099.4 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2101.8 5137 warnings generated.
#9 2101.8 Suppressed 5135 warnings (5135 in non-user code).
#9 2101.8 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2102.6 2733 warnings generated.
#9 2102.6 Suppressed 2733 warnings (2733 in non-user code).
#9 2102.6 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2105.7 5119 warnings generated.
#9 2105.7 Suppressed 5097 warnings (5097 in non-user code).
#9 2105.7 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2105.9 2730 warnings generated.
#9 2105.9 Suppressed 2730 warnings (2730 in non-user code).
#9 2105.9 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2106.6 2473 warnings generated.
#9 2106.6 4946 warnings generated.
#9 2106.6 Suppressed 4946 warnings (4946 in non-user code).
#9 2106.6 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2109.1 3080 warnings generated.
#9 2109.1 Suppressed 3077 warnings (3077 in non-user code).
#9 2109.1 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2109.2 5096 warnings generated.
#9 2109.2 Suppressed 5092 warnings (5092 in non-user code).
#9 2109.2 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2111.0 5083 warnings generated.
#9 2111.0 Suppressed 5074 warnings (5074 in non-user code).
#9 2111.0 Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
#9 2111.1 + exit 0
#9 DONE 2111.2s

[radiomix]

I am missing lines even in the usual view after opening a step: It starts like this:

58  [INFO] Scanning for projects...
59 Warning:

Sometimes even with line 200 ;-//

[radiomix]

AFTER the step is finished I can open the step context which takes the first 57 lines ...
And raw logs only show after the complete JOB is finished (on GHA-runners).

[alexv-smirnov]

Hi. I see job steps are misplaced, and no log published until the step 'Run tests' is complete. I don't even see if that step is running.

Screenshot below corresponds to the https://github.com/ydb-platform/ydb/actions/runs/7615161924/job/20739051067 job run, at the moment when tests were actually running and producing logs. The 'Run tests' is shown as a last one, while it's correctly must be show next to the 'Build' step. Example of a correct order is here: https://github.com/ydb-platform/ydb/actions/runs/7613870165/job/20734827859

[andrewakim]

Hi @alexv-smirnov - It looks like you're using a self-hosted runner for the build_and_test jobs. Can you check to see if your network settings are up-to-date for self-hosted runners?

[rgeorge26]

I love this feature, previously we had to wait for the jobs to complete before we could see the logs

[camptatopenmars]

I don't recall being asked if it was okay to run experiments in my production build environment. NOT COOL AT ALL. I have builds hanging now, it might be me, it might be you. I don't need this. If you feel like experimenting, experiment on free accounts, not things labelled ENTERPRISE.

[eli-persona]

Same feedback as @alexv-smirnov above regarding in-flight step being out of order + no way to see its running logs

Love that this log streaming feature is FINALLY getting out... but not quite there yet ;)

[andrewakim]

Hi @eli-persona - Thanks for reporting this! Are you using a self-hosted runner for this job? If so, do you know if your network access settings are up-to-date? If you can share the run id or URL to the run, that'd be helpful as well. You can share this information using this form instead, if you prefer.

[kewei5zhang]

Hmmm can't see logs, how to disable beta

[andrewakim]

Hi @kewei5zhang - Sorry you're running into this issue. Can you use this form to share a bit more details about what you're experiencing? We were experiencing a separate issue internally so we turned off the streaming logs beta for now. Once things return to normal, we'll turn it back on.

[lancejpollard]

https://webapps.stackexchange.com/questions/173612/is-there-a-screen-which-keeps-the-current-action-logs-for-the-latest-push-on-g

Each set of action logs in my experience in GitHub Actions goes under https://github.com/termsurf/chocolatey-task/actions/runs/7620716992/job/20755895856. Then you have to:

• click "Actions" tab
• click the latest build
• click on the build logs

That's kind of annoying when debugging, is there a screen or way to just keep it on the latest logs?

[anjalichhabra-clarks]

When execution in progress, loading of logs stuck in between. Observed this 3-4times in Beta version and execution takes logner than expected.

"refreshing or navigating away from a running job's logs meant losing that context" -- Now on refresh it doesn't even show the running logs.

"Now, as soon as you open the logs, you'll see the last 1,000 lines, making it simpler to stay updated on job progress and status." -- Remains at 1st line itself for me

[radiomix]

@andrewakim this ^^^ (your) form wants me to log in with Google LOL 🙅

[radiomix]

IS there a way to DEACTIVATE the beta?

[andrewakim]

👋 @radiomix - You should be able to submit a response with the form without logging into anything 🤔. I've double checked the settings and tested it on my end. If you're still having issues with it, can you share your feedback in this post?

This feature is tied to a larger body of work on our side so it's not possible to deactivate only streaming logs without impacting overall log delivery. We've noticed that the majority of issues people are experiencing are due to out-of-date network access configs when using self-hosted runners or a VPN. We're also aware of a bug with some Safari versions where the logs will only update on refresh. Is the issue you're running into related to either of these by chance?

[radiomix]

Thank you for the answer.
My post above about slowness was from a run on a Github runner browsing with a recent Firefox version under Linux. Our colleges experience the same issue with Chrom on Mac-OS.

If the issue is connected to VPN-usage . . . what do you expect me/us to do? Renounce VPN usage . . . ?

[jsoref]

@radiomix afaict, the Google form offers to save progress for people who are logged in but doesn't appear to require it for submissions.

What we've seen elsewhere is that a step that starts a VPN will break logging for that step, which isn't particularly surprising. For future steps, as long as the VPN isn't blocking reporting, logs should be recorded. It should be easy enough to capture the VPN setup step's output and report them in a subsequent step if you need them. And adjusting the VPN to allow access to GitHub's logging endpoint seems like a reasonable requirement.

[arnabca]

Good.

[mjperrone]

I'd like to have case sensitive search of github action log output. Looks like the default is case insensitive.

[asparagusbeef]

Feature suggestion: have a single dashboard for an organization to see all action workflows for the different repositories simultaneously.

[GurayCetin]

job is stuck on more than 1.5 hours and looking as running even it's finished. cancel workflow is not working.

[ludvigeriksson]

It would be nice if you could put an "overflow-y: scroll" on the log section, so that the entire page doesn't scroll

[mccare]

Would be great to fix the Safari bug where the logs are not streamed and only update on page reload. Other option would be to opt out of the beta (I would since the Safari bug is annoying).

[Martin-Gonzalez90]

It would be nice have next to the jobs list an artifact button or section.
Right now having to go to the bottom of it is a bit hidden

[wolfiex]

It would be nice to re-run the jobs, but with the updated (fixed) yml file when debugging.

[fdocr]

The features/behavior in this feature have been awesome.

The things that come to mind that I would like to have are two/three floating buttons in the bottom right (or somewhere around the streaming logs area). These are quick controls that could do things like:

• Return to top
• Jump to end/bottom
• Collapse all steps (summarized view)

[aejuice-github]

When I click "Cancel job" it keeps running for 10-40 minutes. Would be nice not to not to wait!

[Xcopz1]

Feedback

[danielthedifficult]

Perhaps it's only on my machine (macOS Sonoma + Brave 1.64.122 Chromium: 123.0.6312.122 (Official Build) (x86_64) ) but when searching the logs, it shows matches, but it doesn't scroll to them - making the search feature functionally impotent.

[LinqLover]

Text search only finds the first 100 hits - this is not enough sometimes, and the UI does not display that there are further hits (not even a small warning icon or so).

[sidathm]

I'm using AWS CDK to make deployments. It looks like I cannot see the CDK logs that show the deployment progress and the CDK outputs in GitHub Actions anymore

[MCLifeLeader]

I would really like to be able to test my action yaml script changes from my local machine before I commit the change. I'm probably doing it the hard way, but I make a change, commit the change wait for the action to run then try again. Iteration on actions is painful.

Couldn't it function a bit like a "Stash", gather the changes and then submit the action in a sudo PR?