| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
Also split off part of the linux_sandbox_test into the linux_sandbox_network_test.
RELNOTES: None.
PiperOrigin-RevId: 178816110
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Use $(location) to get the unittest.bash script, which allows this test to also
run with a different label prefix. This involves removing the intermediate
testenv.sh script, which doesn't seem to add much value.
We might want to consider a sh_unit_test rule or macro that has an implicit
dependency on the unittest.bash script and doesn't require every test to do
this manually.
PiperOrigin-RevId: 164846477
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
--
MOS_MIGRATED_REVID=133576201
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Neither `realpath` nor `readlink -e` are available
on Mac OS X, so I implemented one using basic Bash
utilities: `readlink`, `basename`, and `dirname`.
I also implemented a `normalize_path` method that
can normalize relative or absolute path strings
(remove and resolve "." and ".." references). It
uses simple string processing and doesn't touch
the file system.
This will help fixing
https://github.com/bazelbuild/bazel/issues/1776 and
also opensourcing some shell tests that rely on
`realpath`.
--
MOS_MIGRATED_REVID=133249912
|
| |
|
|
|
|
|
|
|
|
|
| |
missing file to it.
We need to activate this check on presubmits
--
Change-Id: Ia95e92d3816ce92bb69bc0e2cf56e9c60b68d970
Reviewed-on: https://bazel-review.googlesource.com/#/c/3949/
MOS_MIGRATED_REVID=126404792
|
|
|
This is part of the shell test infrastructure for Bazel. It creates
test suites in Bazel shell. Handling the test ouputs efficiently for
making test summaries.
--
MOS_MIGRATED_REVID=88929067
|
ruperts
ulfjack
Luis Fernando Pino Duque
Laszlo Csomor
Damien Martin-Guillerez