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

	Commit message (Collapse)	Author	Age
*	In terse test_summary, skip no-status tests	Klaus Aehlig	2017-08-30
\| \| \| \| \| \| \| \| \|	If there is a build failure, don't clobber the terse test summary by naming all the (usually many) tests that were skipped due to this failure. Change-Id: I6daae3efb1594c2b1018f87a50cf63949a34535b PiperOrigin-RevId: 166983264
*	Make integration tests more portable	Klaus Aehlig	2017-07-05
\| \| \| \| \| \| \| \|	By avoiding paths that are too specific for a given system, and bringing option arguments before non-option arguments. Change-Id: I82acae94e2d9808c9e81a85018c6a0578da8bd42 PiperOrigin-RevId: 160957203
*	Fix broken test_test on macOS.	philwo	2017-04-26
\| \| \| \| \| \|	"true" is not /bin/true there, it's /usr/bin/true. PiperOrigin-RevId: 154280112
*	Bazel: Fix wrong test count shown for failing tests.	philwo	2017-04-24
	Bazel always miscounted the number of passes that a test was run, resulting in confusing output like this: philwo@philwo:~/src/errortest$ bazel test //tests:fail [...] //tests:fail FAILED in 1 out of 2 in 0.1s ERROR .tests/fail It shows "1 out of 2" even though just one pass happened. With this fix, the output is correct: philwo@philwo:~/src/errortest$ bazel test //tests:fail [...] //tests:fail FAILED in 0.1s ERROR .tests/fail Relevant to #2855. PiperOrigin-RevId: 154043240