Composite actions logs are out of order

[hross]

The logs for composite actions appear to be out of order:

https://twitter.com/crazyws/status/1293525542810025991, https://github.com/crazy-max/ghaction-dump-context/actions

We should put them in the correct order.

[thboop]

Live logs are best effort, and can appear out of order at some times. Will reopen if we see this often.

[jk2K]

I have the same problem

my runner is self hosted,

runner version: 2.286.0
os: CentOS Linux release 7.4.1708 (Core)

yml

name: Demo27
on:
  workflow_dispatch:
    inputs:
      start:
        description: manual start
        default: '0'
jobs:
  job1:
    runs-on: test1
    steps:
      - id: step1
        run: |
          pwd

          echo "${{ github.workspace }}"
          rm -rf "${{ github.workspace }}"/*

          wget https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh

          echo "sudo ls" > install.sh

          bash install.sh

out of order

normal

a bit random, I did not find the pattern of recurrence of the problem

[vincerubinetti]

Not sure if related, but I'm actually getting logs inside of other logs, i.e. "interleaving". It seems to only happen with things that log over multiple lines, like multi-line strings and nested objects.

List:
[
  {
    "key": "value",
    Multi-line error line 1
    Multi-line error line 2
/home/runner/work/blah.js:94
    "key": "value",
  },

console.log("List:");
console.log(list);

console.error("Multi-line error line 1 \nMulti-line error line 2"

Doesn't happen at all when running Node locally.

[wyot1]

Maybe re-open this issue?

I also noticed this peculiarity just now.

Even when executing a single bash script with the following contents:

echo foo
command_do_something
echo bar

It's possible to be out of order, which seems very strange. Not the live log, the plain one after the fact.

That log message should be above the whole thing. It appears out of nowhere.

Now buffering makes sense, but how come the same one can randomly mix itself up?

[AllysonPemberton-UnlikelyAI]

+1 also seeing this issue and it makes it very hard to debug our failing tests