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

	Commit message (Collapse)	Author	Age
*	Omit parts of BEP events (like stdout, stderr) when the associated artifact ↵	tomlu	2018-07-11
\| \| \| \| \| \| \|	uploader cannot upload a particular file. RELNOTES: None PiperOrigin-RevId: 204167372
*	Include more information about build events' referenced local files.	tomlu	2018-07-04
\| \| \| \| \| \| \|	Instead of just a path, events now include information about the type of file (output, source file, stdout/stderr, test logs, etc.). This information can be used by the uploaders to determine a) whether to upload, b) what kind of lease to give the files. RELNOTES: None PiperOrigin-RevId: 203285549
*	Add a mechanism for build event protocol events to upload files	ulfjack	2018-06-15
\| \| \| \| \| \| \| \|	This should be a no-op, mostly replacing PathConverter with BuildEventArtifactUploader, since none of the implementations perform any upload yet. PiperOrigin-RevId: 200685325
*	Add status details to the protos	ulfjack	2018-06-08
\| \| \| \| \| \| \| \|	Both for the build event stream proto, which contains the TestResult event, and to the test status proto which is used for caching. The new field may be populated in the future. PiperOrigin-RevId: 199846232
*	Simplify TestAttempt interface	ulfjack	2018-06-07
\| \| \| \| \| \| \|	By always requiring a TestResultData instace, we simplify the callers, which already have to do all the work anyway. PiperOrigin-RevId: 199639965
*	Rename BuildEventConverters to BuildEventContext	ulfjack	2018-05-17
\| \| \| \| \| \| \|	This is in preparation for adding options to the class, which can be used to modify the behavior of build events posted to the BEP. PiperOrigin-RevId: 196997573
*	Refactor TestAttempt event posting code	ulfjack	2018-05-14
\| \| \| \| \| \| \| \|	For flaky tests, Bazel may have cached information about multiple test attempts. In that case, we might want to post all of them on a subsequent cache hit, rather than posting only the passing attempt. We currently subclass TestResult inside Google, which overrides the new getCachedTestAttempts method. PiperOrigin-RevId: 196491575
*	Add execution information to standalone test results.	Benjamin Peterson	2018-04-26
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In StandaloneTestStrategy, copy as much information as SpawnResult makes available to us through to both the TestResultData and BEP's TestResult.ExecutionInfo protos. One immediate consequence is that the UI and BEP can tell you whether a test result was cached remotely. I changed Executor.getEventHandler to return an ExtendedEventHandler because it makes this change easier to test. Closes #5081. Change-Id: I94fefdcd2e029c81085076736ad13a4bdf1bae8f PiperOrigin-RevId: 194383009
*	BEP: Cached test actions post execution info from TestResult	ulfjack	2018-03-30
\| \| \| \| \| \|	Currently, the TestResult does not have an execution info, but that may change in the future. PiperOrigin-RevId: 191148241
*	BEP: ensure that TestAttempts are reported after their target	Klaus Aehlig	2018-02-07
\| \| \| \| \| \| \| \| \| \|	Ensure that each test attempt is only reported after the report of the completion of the build of the corresponding test target. Normally this should happen anyway, but due to races on the internal event bus, the order of the report might be messed up. So add an explicit order constraint. Change-Id: I4d325bc31a46dcdf8763ba5416b5135a0978536e PiperOrigin-RevId: 184825306
*	Move BazelRuleClassProvider.TESTING_SUPPORT to its own class in rules/test.	lpino	2018-01-29
	PiperOrigin-RevId: 183672444