Self-hosted runners latest version missing logs about when a job was picked up by runner

[awalvie]

Describe the bug
We've been using self-hosted github actions for the better part of a four years now and have been using a script to calculate the total running time of a workflow. This was done because there's a difference between the timestamp when the workflow was created vs the timestamp when it's actually picked up by the runner.

Our script looks for the following in the raw logs for workflows:

2024-02-14T12:00:00.9730417Z Requested labels: docker, self-hosted
2024-02-14T12:00:00.9730886Z Job defined at: repo/workflows/workflow.yml@refs/heads/master
2024-02-14T12:00:00.9731061Z Waiting for a runner to pick up this job...
2024-02-14T12:02:14.9250998Z Job is about to start running on the runner: runner (repository

to get the starting time for a workflow and then would subtract that from the created time to get the actual workflow time.

The above lines seem to have disappeared from the raw logs in the past week. They do show up in the UI before a workflow is picked up by the runner but are missing from logs.

Runner Version and Platform

Version of your runner?

2.314.1

OS of the machine running the runner? OSX/Windows/Linux/...

Linux

What's not working?

Previously

Current:

Not sure if this was intentional. If it was, is there any way to get information about when the job was actually picked up by the runner?

[AdnaneKhan]

Ditto - this broke a security tool I maintain that allows users to monitor for runner group misconfigurations among other issues (such as an unexpected org-level runner suddenly picking up a workflow from a repository that should just have a repository-level self-hosted runner).

[AdnaneKhan]

@awalvie I spent some more time looking into this yesterday and I think the issue is due to the recent change to numbering introduced in the release a week ago. The run log archive zip still has this information - the file name seems to have changed a bit though. In the past all of the combined job log txt files started with ‘0_’, now they start with a number based on the job’s positioning.