Resizing the terminal kills bazel run tests

[the-mikedavis]

Description of the bug:

Resizing the terminal while running bazel run TARGET when TARGET is a test rule makes the bazel process exit with code 156. This doesn't occur when TARGET is an executable but non-test rule.

I can reproduce this on Linux and macOS with Kitty, Alacritty and WezTerm terminal emulators with terms xterm-kitty and xterm-256color. Whether $PAGER is set or not doesn't seem to make a difference.

recording.mp4

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

I put together a MWE here: https://gist.github.com/the-mikedavis/6b34a7f445a30fb34331d1fa19b89201

Most minimally, a directory with an empty WORKSPACE file, a BUILD file with contents like so:

load("//:defs.bzl", "build")
build(name = "hello")

and defs.bzl:

def _impl(ctx):
    output = ctx.actions.declare_file(ctx.label.name)
    script = """echo "..."
    sleep 60
    echo "Hi!"
    """
    ctx.actions.write(
        output = output,
        content = script,
    )
    return [DefaultInfo(executable = output)]

build = rule(
    implementation = _impl,
    test = True,
)

Altogether the directory should look like so:

$ tree .
.
├── BUILD
├── defs.bzl
└── WORKSPACE

3 files

Run bazel run //:hello in this directory. Once you see the "...", resize the terminal. For resizing done through a window manager, you need to resize the terminal twice: the first resize doesn't kill bazel. The bazel process should exit with code 156.

Which operating system are you running Bazel on?

Linux, macOS

What is the output of bazel info release?

release 6.0.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[meisterT]

We probably have to handle the signal here: https://cs.opensource.google/bazel/bazel/+/2f9c7d60ea676f9f8e929b20a3ff74e786995c91:src/main/cpp/blaze_util_posix.cc;l=134

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 30 days. It will be closed in the next 7 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler".

[brentleyjones]

Not stale.