bazel - a fast, scalable, multi-language and extensible build system

	Commit message (Collapse)	Author	Age
*	Delete switch for nested set serialization. It's fast enough to be on by ↵	janakr	2018-06-19
\| \| \| \| \| \|	default. PiperOrigin-RevId: 201218341
*	Add some minor debugging messages to discard_analysis_cache_test, ↵	janakr	2017-11-29
\| \| \| \| \| \| \| \|	purportedly to diagnose issue #4181. My real hope is to achieve the effect I got in discard_graph_edges_test, where the debugging messages seem to have made the flakiness go away, but since this is less multithreaded, I'm less hopeful. PiperOrigin-RevId: 177325229
*	Migrate tests to ctx.actions.run/run_shell.	dslomov	2017-07-05
\| \| \| \| \|	RELNOTES: None. PiperOrigin-RevId: 160817326
*	Introduce ctx.actions.write in place of ctx.file_action.	dslomov	2017-06-30
\| \| \| \| \|	RELNOTES: None. PiperOrigin-RevId: 160630261
*	Add 'ctx.actions' and implement 'ctx.action.declare_file'.	dslomov	2017-06-27
\| \| \| \| \|	RELNOTES: None. PiperOrigin-RevId: 160264501
*	Clear AspectValues when discarding analysis cache, along with ↵	janakr	2017-03-29
\| \| \| \| \| \| \| \|	ConfiguredTargetValues. Also clear transitive packages for both, even for top-level targets. This is not expected to save significant memory, but is expected to reduce the number of references to Packages, allowing them to be dropped more easily when discarding analysis cache and running in batch mode. PiperOrigin-RevId: 151508877
*	Create a proper wrapper script for executing "bazel" in the integration tests.	Luis Fernando Pino Duque	2016-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
*	Open source discard_analysis_cache_test.	Tobias Werth	2016-09-13
	-- MOS_MIGRATED_REVID=132965047