| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
removed "sychronized" from Reporter.handle() as we want to be able to let
EventHandlers care about their own synchronization.
RELNOTES: None.
PiperOrigin-RevId: 208628638
|
|
|
|
|
|
|
|
|
| |
...in a single event instead of relying on the synchronisation on the
reporter. In this way, it will be possible to focus on output of errors,
and also to deduplicate warnings.
Change-Id: I9669e8497ca6e22a01f3e285ec9ee42c1ecf3fb5
PiperOrigin-RevId: 208223882
|
|
|
|
|
|
|
| |
Turns out, my previous search expression didn't find the ones that were not "final LOG" or "final log" and a surprising number of places were missing the "final" tag.
RELNOTES: None.
PiperOrigin-RevId: 167547507
|
|
|
|
|
|
|
| |
This removes our dependency on third_party/joda_time, which can be removed in the next commit.
Change-Id: Ibda131d34d0abdc2d675db4bfbd2e99480c055ee
PiperOrigin-RevId: 167515260
|
|
|
|
|
| |
RELNOTES: The `print` function now prints debug messages instead of warnings.
PiperOrigin-RevId: 164880003
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 149061874
MOS_MIGRATED_REVID=149061874
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119051781
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Manual breaking lines was introduced in a49f0253 to ensure Bazel knows
the number of lines written, so the correct number of lines can be
erased when the progress bar is updated. As this is only an issue if curses
are in use, that wrapping as only added to the FancyTerminalEventHandler.
However, Bazel distinguishes between two uses of curses
- curses to add color to the output, and
- curses to control the cursor and erase outdated progress bars.
If the former is used, but not the latter, it is not necessary to wrap
lines; in fact, not doing so is more backwards compatible while still
keeping the line-eating bug fixed. So don't break lines in this case.
--
Change-Id: Ieef8ab9410a071c35609a395f45cd56653115426
Reviewed-on: https://bazel-review.googlesource.com/#/c/3170
MOS_MIGRATED_REVID=118587980
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Manually break lines in the progress bar (and only in the progress bar!)
that are longer than the terminal width. In this way, we avoid any
confusion about when the terminal advances a line; in particular, when
the terminal is wider than we believe, we do not erase back into the
scrollback buffer.
--
Change-Id: I19f21bdbd6e6af4665d1e712b921f1a15c7d901c
Reviewed-on: https://bazel-review.googlesource.com/#/c/3041
MOS_MIGRATED_REVID=116138487
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108324961
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107582017
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102239051
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=89134285
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87821306
|
|
--
MOE_MIGRATED_REVID=85702957
|