bazelbuild/bazel

`--curses=no` has almost no information about analysis phase

Open

#23.522 aberto em 5 de set. de 2024

Ver no GitHub
 (2 comments) (1 reaction) (0 assignees)Java (4.465 forks)batch import
P3help wantedteam-CLItype: feature request

Métricas do repositório

Stars
 (25.384 stars)
Métricas de merge de PR
 (Mesclagem média 22d 20h) (77 fundiu PRs em 30d)

Description

Description of the feature request:

When specifying --curses=no, there's almost no information about the analysis phase (what's being downloaded, while repo rules and modexts are being executed etc.) printed. That's a shame, as --curses=yes has a lot of interesting info about that.

Which category does this issue belong to?

No response

What underlying problem are you trying to solve with this feature?

GitHub actions logs with --curses=auto behaves as --curses=no, which makes our CI logs not very useful when it comes to guesstimating what's going on in the analysis phase.

Which operating system are you running Bazel on?

Ubuntu 22.04

What is the output of bazel info release?

7.3.1

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 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

Guia do colaborador