aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java/com/google/devtools/build/lib/runtime
Commit message (Collapse)AuthorAge
* Make exception in case a test tries to remote-log more informative.Gravatar Janak Ramakrishnan2015-09-17
| | | | | -- MOS_MIGRATED_REVID=103290841
* Simplify BuildView construction and store configurations in the build result.Gravatar Ulf Adams2015-09-17
| | | | | | | | | | | | | | | I was persuing the idea that BuildView could become stateless. While that should be possible, we're currently still relying on minimal state in BuildView (from tests at least) in a way that makes it tricky to remove. Instead, I'm now trying to move the BuildView into CommandEnvironment, and create a new one as needed (only for build commands); that makes it safe in the presence of concurrently running commands, as long as they don't use the same BuildView instace. (Of course, allowing commands to run concurrently will need more changes outside of BuildView.) -- MOS_MIGRATED_REVID=103279370
* Make the module environment invoked exit code path thread-safe.Gravatar Ulf Adams2015-09-17
| | | | | | | | | | The module environment can be called from any number of threads, not necessarily from the main thread. I don't know if it's a problem right now - we don't have any problem reports that could be caused by this - but better be safe than sorry. -- MOS_MIGRATED_REVID=103277567
* Remove the now-unused BlazeModule.beforeCommand variant.Gravatar Ulf Adams2015-09-17
| | | | | -- MOS_MIGRATED_REVID=103276489
* Move the clientEnv to the CommandEnvironment.Gravatar Ulf Adams2015-09-17
| | | | | -- MOS_MIGRATED_REVID=103269584
* Move several parts of BlazeRuntime to CommandEnvironment.Gravatar Ulf Adams2015-09-16
| | | | | | | | The main piece is the blaze module environment, which is only valid during command execution. Also configuration creation and precompleteCommand. -- MOS_MIGRATED_REVID=103186467
* Change checkRuntime to take a CommandEnvironment instead.Gravatar Ulf Adams2015-09-16
| | | | | | | | | I wanted to merge it into beforeCommand, but the reporter isn't set up yet when we call beforeCommand. Hopefully we can refactor the code to merge it in the future. -- MOS_MIGRATED_REVID=103179268
* Change most calls to BlazeRuntime.getReporter() to use CommandEnvironment.Gravatar Ulf Adams2015-09-16
| | | | | -- MOS_MIGRATED_REVID=103175472
* Introduce CommandEnvironment and pass it instead of BlazeRuntime.Gravatar Ulf Adams2015-09-15
| | | | | | | | The very long term plan is to make BlazeRuntime immutable, so that we can run multiple commands in the same server. -- MOS_MIGRATED_REVID=103080946
* Use AutoProfiler in the Bazel codebase.Gravatar Nathan Harmata2015-09-08
| | | | | -- MOS_MIGRATED_REVID=102584924
* Allow canonicalize-flags to run for any command.Gravatar Ulf Adams2015-09-08
| | | | | -- MOS_MIGRATED_REVID=102483838
* Remove test warning filtering.Gravatar Eric Fellheimer2015-09-04
| | | | | -- MOS_MIGRATED_REVID=102345574
* Code cleanupGravatar Laurent Le Brun2015-09-03
| | | | | -- MOS_MIGRATED_REVID=102239051
* Collect Skylark profile info and create HTML statistics when --html_details ↵Gravatar Googler2015-09-02
| | | | | | | given -- MOS_MIGRATED_REVID=102046602
* Drop the baseline artifact output group.Gravatar Ulf Adams2015-08-31
| | | | | | | | | | The baseline artifacts are part of the instrumented files provider now, and are strongly tied to the collect_code_coverage flag. It seems to be simpler to collect them explicitly in the BuildView (which already collects them for post-processing), than to rely on the output group selection. -- MOS_MIGRATED_REVID=101926341
* Be resilient to a non-decreasing clock in ↵Gravatar Nathan Harmata2015-08-28
| | | | | | | | | BlazeRuntime#recordLastExecutionTime. Also add @Nullable annotations as appropriate. Fixes #394. -- MOS_MIGRATED_REVID=101685096
* Description redacted.Gravatar Marian Lobur2015-08-17
| | | | | -- MOS_MIGRATED_REVID=100814605
* Resolve TODO in BlazeCommandEventHandlerGravatar Michajlo Matijkiw2015-08-13
| | | | | -- MOS_MIGRATED_REVID=100494619
* Remove broken code.Gravatar Marian Lobur2015-08-13
| | | | | | | | 1. We are adding handler and removing it after that. 2. There is no modules that calls .handle method of reporter in beforeCommand. -- MOS_MIGRATED_REVID=100478454
* Allow runtime introspection of a content hash of the Blaze binary and all ↵Gravatar Eric Fellheimer2015-08-12
| | | | | | | embedded binaries. -- MOS_MIGRATED_REVID=100476182
* Log instead of crash report on failure in BlazeCommandEventHandlerGravatar Michajlo Matijkiw2015-08-05
| | | | | | | This isn't really a crash, so don't report a crash, just log locally and remotely. -- MOS_MIGRATED_REVID=99857034
* Crash in tests if anybody tries to log remotely. Remote logging usually ↵Gravatar Janak Ramakrishnan2015-08-04
| | | | | | | indicates an error, and tests shouldn't normally have such errors. -- MOS_MIGRATED_REVID=99789434
* Fixed bug where blaze run with the --color=no flag was still printing out in ↵Gravatar Shreya Bhattarai2015-08-04
| | | | | | | | | color when the build fails. Includes fix for problems causing the original slowdown to blaze query -- MOS_MIGRATED_REVID=99755414
* Send bug report on IOException in BlazeCommandEventHandler instead of ignoringGravatar Michajlo Matijkiw2015-08-04
| | | | | | | | Don't log the actual message in interest of not spamming logs, for now. We can use how common this is to determine if crashing is appropriate. -- MOS_MIGRATED_REVID=99587448
* Rollback of commit 2e7a5b47979b2679208a97a65df265be953eb595.Gravatar Han-Wen Nienhuys2015-08-04
| | | | | | | | | *** Reason for rollback *** Query performance regression. -- MOS_MIGRATED_REVID=99560234
* Add "warm" starting to mobile-install.Gravatar Googler2015-08-04
| | | | | | | | | | | | | | | | | | This introduces a new way to stop applications when deploying incremental changes that saves the current app state for the next run. This allows things like the back stack, and View/Fragment/Activity saved state to be restored when the app next launches, making it easier to quickly iterate on code changes. It adds a "--start" flag to mobile-install that replaces "--start_app". --start accepts an argument describing the mode: no, cold, or warm. "no" is now the equivalent of "--nostart_app", "cold" is the equivalent of "--start_app", and "warm" is the new start mode. Note that this is only useful with incremental installs, as Android clears out any previously saved state when an APK is replaced. -- MOS_MIGRATED_REVID=99508790
* Remove vestigial references to 32-bit/64-bit binaries.Gravatar Janak Ramakrishnan2015-07-30
| | | | | -- MOS_MIGRATED_REVID=99411524
* Allow modules to specify additional nodes in the graph to be invalidated and ↵Gravatar Janak Ramakrishnan2015-07-29
| | | | | | | | | | | use this functionality to properly invalidate http download nodes if the downloaded zip file doesn't match the specified hash. This still means that the actual files downloaded may not match, but checking all such files may be too expensive. This helps with #336 but before that issue can be closed all remote repositories (git, etc.), should have similar functionality added. -- MOS_MIGRATED_REVID=99317085
* Record the project file used to the master log.Gravatar Googler2015-07-28
| | | | | -- MOS_MIGRATED_REVID=99224654
* Fix conversion from nanoseconds so that it actually targets milliseconds. ↵Gravatar Nathan Harmata2015-07-28
| | | | | | | The incorrect conversion was introduced recently. -- MOS_MIGRATED_REVID=99218016
* Record time spent loading action cache in INFO log.Gravatar Nathan Harmata2015-07-28
| | | | | -- MOS_MIGRATED_REVID=99198288
* Don't choke on Exceptions that have a null error message.Gravatar Han-Wen Nienhuys2015-07-27
| | | | | -- MOS_MIGRATED_REVID=99174214
* Fixed bug where blaze run with the --color=no flag was still printing out in ↵Gravatar Googler2015-07-21
| | | | | | | color when the build fails. -- MOS_MIGRATED_REVID=98736813
* Say explicitly that --config=X ignores non-existent .rc file config sections.Gravatar Laszlo Csomor2015-07-17
| | | | | -- MOS_MIGRATED_REVID=98394325
* Throw InterruptedException directly if a query is interrupted, instead of ↵Gravatar Janak Ramakrishnan2015-07-10
| | | | | | | | | wrapping it in a QueryException. QueryException should usually indicate a persistent failure, while an InterruptedException is transient. Wrapping the InterruptedException in a QueryException just obfuscates state. -- MOS_MIGRATED_REVID=97815388
* Remove the option for adding multiple --tool_tag options.Gravatar Googler2015-07-10
| | | | | -- MOS_MIGRATED_REVID=97800307
* Make globs work in remote repositories.Gravatar Lukacs Berki2015-07-08
| | | | | | | | | | | This involved quite a few changes, mainly changing a bunch of places where we refer to packages by a PathFragment to PackageIdentifier. The only wart is the code in PathPackageLocator: ideally, it would just call into PackageLookupFunction. Unfortunately, it is (through globbing and Parser.include) called from within a Skyframe function, and we don't want to have two eval() calls going on at the same time, so we cannot use that. There is a potential correctness issue there: PathPackageLocator now assumes where external repositories are put and assumes that they are there when it gets control, but my understanding is that the associated RepositoryValue is always evaluated before, so it works out okay. -- MOS_MIGRATED_REVID=97751539
* Rollback of accidentally submitted change.Gravatar Lukacs Berki2015-07-07
| | | | | -- MOS_MIGRATED_REVID=97648982
* Make globs work in remote repositories.Gravatar Lukacs Berki2015-07-07
| | | | | | | | | | | This involved quite a few changes, mainly changing a bunch of places where we refer to packages by a PathFragment to PackageIdentifier. The only wart is the code in PathPackageLocator: ideally, it would just call into PackageLookupFunction. Unfortunately, it is (through globbing and Parser.include) called from within a Skyframe function, and we don't want to have two eval() calls going on at the same time, so we cannot use that. There is a potential correctness issue there: PathPackageLocator now assumes where external repositories are put and assumes that they are there when it gets control, but my understanding is that the associated RepositoryValue is always evaluated before, so it works out okay. -- MOS_MIGRATED_REVID=97647787
* Description redacted.Gravatar Googler2015-06-24
| | | | | -- MOS_MIGRATED_REVID=96703011
* Add dump commandGravatar Kristina Chodorow2015-06-15
| | | | | -- MOS_MIGRATED_REVID=95843033
* Description redacted.Gravatar Lukacs Berki2015-06-10
| | | | | -- MOS_MIGRATED_REVID=95615442
* Add --with_aspect_deps flag to blaze query. This flag should produce ↵Gravatar Lukacs Berki2015-06-05
| | | | | | | | | | | | | additional information about aspect dependencies when --output is set to {xml, proto}. One quirk of this CL is that if BUILD files of direct dependencies are added both under <subinclude> and <load>. Any better ideas are appreciated. As a drive-by fix, if for some reason a package reports the same label as a both subinclude and a Skylark dependency, it will only be reported once in the proto output. RELNOTES[NEW]: added --with_aspect_deps to blaze query, that prints additional information about aspects of target when --output is set to {xml, proto, record}. -- MOS_MIGRATED_REVID=95272042
* Fix product name in the error message for invalid commands.Gravatar Laszlo Csomor2015-06-03
| | | | | | | | $ bazel blah Command 'blah' not found. Try 'bazel help'. -- MOS_MIGRATED_REVID=95089307
* Initial checkin of the "mobile-install" command.Gravatar Lukacs Berki2015-05-29
| | | | | | | This was omitted when the bulk of the code was moved in order not to pollute the output of "bazel help" with a useless command, but now it is in the way of testing Android functionality. -- MOS_MIGRATED_REVID=94747309
* Remove 'blaze doc_ext' command.Gravatar Laurent Le Brun2015-05-18
| | | | | | | | | We prefer to focus on the web documentation instead. RELNOTES[INC]: 'blaze doc_ext' command removed. -- MOS_MIGRATED_REVID=93871336
* Create a --fetch option to allow fetching during the build commandGravatar Kristina Chodorow2015-05-15
| | | | | -- MOS_MIGRATED_REVID=93639664
* RELNOTES: The --skyframe flag is now deprecated and will be removed in an ↵Gravatar Janak Ramakrishnan2015-05-15
| | | | | | | upcoming release. -- MOS_MIGRATED_REVID=93328637
* Fix info-keys help output.Gravatar Thiago Farina2015-05-08
| | | | | | | | | | | | | | Tested on Linux with the following command line: $ bazel help info-keys | sort | uniq -c And compared the output before and after. Fixes #175 -- Change-Id: Ia879796abf6f5b6b5742bfc9574d64fe53a650a3 MOS_MIGRATED_REVID=93127869
* Don't allow launching from a directory with a space in the nameGravatar Kristina Chodorow2015-04-30
| | | | | | | Further improvements on #167. -- MOS_MIGRATED_REVID=92459390
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-10 00:40:37 +0000