Runner v2.276.0 fails to open some stderr/stdout streams

[thboop]

Describe the bug
The newest runner version may fail to open some stderr/stdout streams. You can't typically open() a socket, and it looks like the stderr stream may be getting kept as a socket now.

To Reproduce
Run a ubuntu runner with the following yaml

name: CI test

on: push

jobs:
  build:
    name: test
    runs-on: self-hosted
    steps:
    - name: test tee /dev/stderr
      run : |
        set -x
        set -euo pipefail
        seq 0 10 | tee /dev/stderr | xargs echo

It will fail with tee: /dev/stderr: No such device or address
Expected behavior
The stderr stream should open and this should not fail.

Runner Version and Platform

v2.276.0 on Ubuntu.

Other information

Looks like it may be related to the .net upgrade
dotnet/runtime#46469

[zen0wu]

Got bitten by this! @thboop Is there any way we could quickly fix this to unblock our CI?

[thboop]

Hey @zen0wu , I'm working on rolling a new version right now, hope to have it available to all users in the next day or so!

Sorry to hear this is impacting your builds, I hope to have this ready asap!

[zen0wu]

@thboop Thank you!

What's broken for us is when we do echo foo > /dev/stderr, I wonder if just removing removing > /dev/stderr and do a normal echo would fix this? I can try myself, but figured it'd be quicker to check with you.

[TingluoHuang]

@zen0wu echo foo >&2 still work, only /dev/stderr is broken

[thboop]

This is in the process of rolling out and all runners should be upgraded in the next day or so.

[thboop]

Should be fixed for everyone now!