search

bazelbuild / bazel

a fast, scalable, multi-language and extensible build system
https://bazel.build
Apache License 2.0
23.29k stars 4.09k forks source link

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

Open criemen opened 2 months ago

criemen commented 2 months ago

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

criemen commented 2 months ago

sample log from the analysis phase from our CI (note the spurious newlines):

Starting local Bazel server and connecting to it...
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 1 packages loaded
Analyzing: target //go:gen (2 packages loaded, 0 targets configured)
Analyzing: target //go:gen (2 packages loaded, 0 targets configured)

Analyzing: target //go:gen (91 packages loaded, 9 targets configured)

Analyzing: target //go:gen (110 packages loaded, 1275 targets configured)

Analyzing: target //go:gen (153 packages loaded, 5197 targets configured)

Analyzing: target //go:gen (155 packages loaded, 7554 targets configured)

Analyzing: target //go:gen (157 packages loaded, 17120 targets configured)

Analyzing: target //go:gen (162 packages loaded, 17149 targets configured)

Analyzing: target //go:gen (166 packages loaded, 17229 targets configured)

Analyzing: target //go:gen (166 packages loaded, 17229 targets configured)

INFO: Analyzed target //go:gen (194 packages loaded, 17411 targets configured).
criemen commented 2 months ago

Forcing --curses=yes on Actions blows up terribly, and does not lead to readable logs either.