| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:bazel_testjobs_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: Ia12a01f27ee8bd5a00aead546bcaf483fc4d72a3
Closes #5835.
Change-Id: I6e9af9da9221a4d4d553e8ad066b607a54c5c907
PiperOrigin-RevId: 208034351
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding and removing hard links to a file from several processes
simultaneously appears to occasionally fail on macOS.
This commit changes the testjobs's test's strategy of keeping track
of the number of tests running in parallel. Instead of counting the
number of links to a shared file, it now counts the number of files
in a shared directory. Instead of each test run adding and removing
a link to a shared file, each run adds and removes a file from a
directory.
--
Change-Id: Idc0a9a9cf1c2f5b03221fcd991e4bf0155e62841
Reviewed-on: https://bazel-review.googlesource.com/c/7392/
MOS_MIGRATED_REVID=139384412
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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=132985974
|
Laszlo Csomor
Mark Schaller
Luis Fernando Pino Duque
Yue Gan