| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
child of the process where the Blaze client itself was run.
Limitations:
- Untested on Windows; it should work because ExecuteProgram() is implemented there, too, but since Windows doesn't support exec(), there is at least one process in between
Progress towards #2815.
RELNOTES[NEW]: The new "--direct_run" flag on "blaze run" lets one run interactive binaries.
PiperOrigin-RevId: 184528845
|
|
|
|
|
|
|
|
| |
Blaze had its own class to avoid GC from varargs array creation for the precondition happy path. Guava now (mostly) implements these, making it unnecessary to maintain our own.
This change was almost entirely automated by search-and-replace. A few BUILD files needed fixing up since I removed an export of preconditions from lib:util, which was all done by add_deps. There was one incorrect usage of Preconditions that was caught by error prone (which checks Guava's version of Preconditions) that I had to change manually.
PiperOrigin-RevId: 175033526
|
|
|
|
|
|
|
| |
Turns out, my previous search expression didn't find the ones that were not "final LOG" or "final log" and a surprising number of places were missing the "final" tag.
RELNOTES: None.
PiperOrigin-RevId: 167547507
|
|
|
|
|
|
|
|
|
|
|
|
| |
While a sentence like "bazel ran out of memory and crashed" should be
human-readable enough, it seems that users often only scan for the word
ERROR in the output and assume everything is fine, if it doesn't occur.
Things get worse, if that procedure is scripted. While these kind of behaviors
should be discouraged, mitigate the consequences by providing mainstream error
messages.
Change-Id: I5a032360881c53575bfbd37a471b96933622d3c5
PiperOrigin-RevId: 160385223
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146305727
MOS_MIGRATED_REVID=146305727
|
|
|
|
|
|
|
|
|
| |
if the product name is null, which is the case for some
integration tests.
--
PiperOrigin-RevId: 146252594
MOS_MIGRATED_REVID=146252594
|
|
|
|
|
|
|
|
|
|
| |
Async threads are divorced from the server's error-reporting mechanism. In the event
of a server shutdown originating in an async-thread, write the exit code to a file that
can be read by the client.
--
PiperOrigin-RevId: 141920284
MOS_MIGRATED_REVID=141920284
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a new "shutdown on crash" hook to the Blaze modules and call it when we
exit due to a crash. This allows modules to perform necessary cleanup of
internal state when exiting abruptly.
Note that the need for implementing "shutdown on crash" is rare. As an
example of when this may be useful is a module that has spawned background
threads to communicate with a remote server and we want to shut down those
connections in a controlled manner.
--
MOS_MIGRATED_REVID=136330678
|
|
|
|
|
|
|
| |
exception that caused the crash is an OOM. Too many systems wrap Errors in other exceptions, for instance https://github.com/google/guava/blob/master/guava-gwt/src-super/com/google/common/cache/super/com/google/common/cache/LocalCache.java#L267
--
MOS_MIGRATED_REVID=127845350
|
|
|
|
|
|
|
|
|
| |
BlazeRuntime#getProductName() or a reference to TestConstants.PRODUCT_NAME for tests.
This CL prepares the codebase in order to delete the constant.
--
MOS_MIGRATED_REVID=122993568
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch replaces the usage of hardcoded "Blaze" string by
Constants.PRODUCT_NAME, so when presenting the output to the user
in the open source version, it says "Bazel" instead of "Blaze",
as "Blaze" is the internal name of the tool and "Bazel" the public
one.
Closes #842
--
Change-Id: I2917656d5254fe34b2761d6e2c79deef7c7fb8a5
Reviewed-on: https://bazel-review.googlesource.com/c/3103/
MOS_MIGRATED_REVID=118042541
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117139503
|
|
|
|
|
|
|
|
|
| |
second time. If the first call is notifying listeners that the command is complete, the second call can overtake it (since it skips notifying listeners) and kill the JVM prematurely.
This change does open up the possibility that the CommandCompleteEvent triggers a hang or blocking process that prevents us from exiting, but I'm not aware of any known cases of that.
--
MOS_MIGRATED_REVID=116053085
|
|
|
|
|
|
|
| |
Reduces garbage.
--
MOS_MIGRATED_REVID=109914243
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=103869828
|
|
|
|
|
|
|
| |
See associated bug for more details.
--
MOS_MIGRATED_REVID=86708715
|
|
--
MOE_MIGRATED_REVID=85702957
|