| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:ui_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I6667e55f26b9f87437234ba949a521760cfaaa18
Closes #5872.
Change-Id: I6667e55f26b9f87437234ba949a521760cfaaa18
PiperOrigin-RevId: 208476786
|
| |
|
|
|
|
|
|
|
|
|
| |
As nobody uses bazel on a traditional teletyper terminal, we
can as well use the line ending of native files instead of
terminal/network line endings. While the console output is not
meant to be handled by anything but a terminal, this still seems
to be done.
Change-Id: Ied745eeedaec70572ef4b3a3c716a0cf57dfdfd1
PiperOrigin-RevId: 207511649
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently a call to "bazel" in an integration test means calling a (quite
hidden) function in test-setup.sh which actually calls "$bazel" defined
in "shell/bazel/testenv.sh" which is equal to "$(rlocation io_bazel/src/bazel)".
This is extremely confusing and error prone.
The new mechanism is to add a wrapper script to shell/bin called bazel
and export this directory to the PATH.
Moreover, not every test loads the same test environment, for instance consider
how bazel_query_test loads the test environment:
- Load shell/integration/testenv.sh which loads,
- shell/bazel/test-setup.sh which loads,
- shell/bazel/testenv.sh which loads,
- shell/unittest.bash which loads,
- shell/testenv.sh
Again this is error prone and specially hard to understand, in fact
each test writer needs to decide which of these testenv to load.
This change fixes all of this by having only one testenv.sh
and summarizing the test setup in integration_test_setup.sh.
Namely, for any new integration test, the developer
needs to load integration_test_setup to get the environment set up including
the unittest framework (also it helps to attract contributions).
This change also allows to open sourcing client_sigint_test: Since bazel was a
function client_sigint_test was using a wrong process id to interrupt
the build. The problem is that $! returns
bash's id instead of the id of the process running in the background
when using a function instead of an executable.
A few tests needed to be adapted to the new infrastructure.
--
MOS_MIGRATED_REVID=136470360
|
|
|
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
|
Laszlo Csomor
Klaus Aehlig
Luis Fernando Pino Duque