aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/test/shell/bazel/bazel_workspace_status_test.sh
Commit message (Collapse)AuthorAge
* Rollback https://github.com/bazelbuild/bazel/pull/5007Gravatar cparsons2018-04-16
| | | | | | | It breaks downstream rules_nodejs. See https://github.com/bazelbuild/bazel/issues/5028 for details. RELNOTES: None. PiperOrigin-RevId: 193074798
* CommandBuilder: remove useShell and setWorkingDirGravatar Laszlo Csomor2018-04-12
| | | | | | | | | | | | | | | | | | | | | Remove the .useShell method, expect callers to just pass the shell interpreter if they need it. This removes the argument vector transformation heuristic, and stops shelling out to cmd.exe on Windows. Also remove the .setWorkingDir method because callers always had to set the working directory. Instead, the CommandBuilder constructor takes the working directory. Closes #2190. (Test code still shells out to cmd.exe though.) Closes #5007. Change-Id: I545e01c811daaf34913cb585492923da81aa02ee PiperOrigin-RevId: 192611370
* Re-evaluate workspace status when clientEnv changesGravatar Justin Santa Barbara2018-03-06
| | | | | | | | | | | | We pass the clientEnv to the workspace status command, and it may use environment variables to influence status. We must therefore reevaluate the workspace status command whenever the clientEnv changes. Fixes #4222 Closes #4705. PiperOrigin-RevId: 187988847
* bazel_workspace_status_test: don't assume orderGravatar Justin Santa Barbara2018-03-01
| | | | | | | | | | | The test_errmsg test tested the behaviour when workspace_status_command was set to a file that did not exist, but other tests created a file with that name. If test_errmsg did not run first, the workspace_status_command would be valid and the test would fail. Closes #4704. PiperOrigin-RevId: 187470549
* Fixes this test for CI.Gravatar Yue Gan2017-03-23
| | | | | | | | It turns out expect_log doesn't work as I expected.. -- PiperOrigin-RevId: 151016907 MOS_MIGRATED_REVID=151016907
* Fixes this test for CI.Gravatar Yue Gan2017-03-23
| | | | | | -- PiperOrigin-RevId: 151001913 MOS_MIGRATED_REVID=151001913
* Display an error message when there is a status command errorGravatar Kristina Chodorow2017-03-17
| | | | | | | | This was printing, fairly unhelpfully `ERROR: Process exited with status 127.` when the .sh file did not exist. -- PiperOrigin-RevId: 150344684 MOS_MIGRATED_REVID=150344684
* Create a proper wrapper script for executing "bazel" in the integration tests.Gravatar Luis Fernando Pino Duque2016-10-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Split the workspace status keys into stable and volatile parts based on if ↵Gravatar Lukacs Berki2016-09-23
| | | | | | | | | they are prefixed with STABLE_. Fixes #1758 . -- MOS_MIGRATED_REVID=134058125
* Rationalize copyright headersGravatar Damien Martin-Guillerez2015-09-25
| | | | | | | | | | | 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
* Fix BUILD_SCM_* being looked for in the stable status file and test it.Gravatar Brian Silverman2015-09-11
| | | | | | | | | | | | They're actually in the volatile status file, which is where it seems like they belong. Fixes #216. -- Change-Id: Ibec7737538ff5c1003b61d1bd3396948c61886de Reviewed-on: https://bazel-review.googlesource.com/1950 MOS_MIGRATED_REVID=102791996
* Add a test for the correct handling BUILD_SCM_STATUS in the workspace status ↵Gravatar Lukacs Berki2015-07-08
| | | | | | | command. -- MOS_MIGRATED_REVID=97766808
* Fix up BazelWorkspaceStatusAction.equals() so that it returns false if the ↵Gravatar Lukacs Berki2015-07-08
workspace status command changes. Fixes #284. -- MOS_MIGRATED_REVID=97766038
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-26 10:08:11 +0000