| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118775810
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/java/com/google/devtools/build/lib:analysis_test
This target is timeout flaky and internally we used 2 shard for
it, let do the same for the OSS test suite now we have the java
test launcher.
Fixes #1112.
--
MOS_MIGRATED_REVID=118768231
|
|
|
|
|
|
|
| |
Fixes #855.
--
MOS_MIGRATED_REVID=118711400
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118699141
|
|
|
|
|
|
|
|
| |
This is problematic for coming up with a less stateful BlazeModule API, which
- in turn - is a requirement for running multiple commands in the same server.
--
MOS_MIGRATED_REVID=118696892
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--java_langtools=@bazel_tools//tools/jdk:langtools
--javabuilder_top=@bazel_tools//tools/jdk:JavaBuilder_deploy.jar
--singlejar_top=@bazel_tools//tools/jdk:SingleJar_deploy.jar
--genclass_top=@bazel_tools//tools/jdk:GenClass_deploy.jar
--ijar_top=@bazel_tools//tools/jdk:ijar
--javac_bootclasspath=@bazel_tools//tools/jdk:bootclasspath
--javac_extdir=@bazel_tools//tools/jdk:extdir
--java_toolchain=@bazel_tools//tools/jdk:toolchain
--host_javabase=@bazel_tools//tools/jdk:jdk
--javabase=@bazel_tools//tools/jdk:jdk
--
MOS_MIGRATED_REVID=118692509
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Treat SUBCOMMAND events the same way as ERROR/WARNING/INFO commands in the
experimental UI: they provide information the user wants to look up later.
As SUBCOMMAND events are only raised if that information is requested by the
user, providing this information does run the risk over overwhelming the user
with information.
--
Change-Id: Ia7adeb2d5b92f18b8b88b026f790ac2af47b59d4
Reviewed-on: https://bazel-review.googlesource.com/#/c/3201
MOS_MIGRATED_REVID=118678085
|
|
|
|
|
|
|
|
|
| |
This is conceptually better (because each fragment should be
self-contained), and gives us better performance, as we no longer need to
load all explicit labels.
--
MOS_MIGRATED_REVID=118674470
|
|
|
|
|
|
|
|
|
| |
This test has been flaky for a long time and does not test what it is supposed to test.
Fixes #248.
--
MOS_MIGRATED_REVID=118668487
|
|
|
|
|
|
|
| |
Constants.DEFAULT_PACKAGE_PATH.
--
MOS_MIGRATED_REVID=118666575
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118662172
|
|
|
|
|
|
|
| |
This is done by adding a default workspace suffix.
--
MOS_MIGRATED_REVID=118656979
|
|
|
|
|
|
|
| |
parsing for it is not broken.
--
MOS_MIGRATED_REVID=118654985
|
|
|
|
|
|
|
|
|
|
|
| |
Also remove a try-catch block, which was converting all configuration
creation errors to IllegalStateException.
This uncovered a bug in CppOptions, which wasn't adding host_grte_top to the
set of explicit labels.
--
MOS_MIGRATED_REVID=118654358
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118605600
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
it more with respect to the new parse_headers feature, ideas I have about
configurable attributes etc.
I am trying to keep functional changes to a minimum. Functional changes
that couldn't really be easily avoided:
- Find correct rule for headers through filegroups
- Find correct target to build even if sources are missing. A proper error is
reported in the subsequent loading phase
Also remove SrcTargetUtil as it is no longer used.
--
MOS_MIGRATED_REVID=118589517
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Manual breaking lines was introduced in a49f0253 to ensure Bazel knows
the number of lines written, so the correct number of lines can be
erased when the progress bar is updated. As this is only an issue if curses
are in use, that wrapping as only added to the FancyTerminalEventHandler.
However, Bazel distinguishes between two uses of curses
- curses to add color to the output, and
- curses to control the cursor and erase outdated progress bars.
If the former is used, but not the latter, it is not necessary to wrap
lines; in fact, not doing so is more backwards compatible while still
keeping the line-eating bug fixed. So don't break lines in this case.
--
Change-Id: Ieef8ab9410a071c35609a395f45cd56653115426
Reviewed-on: https://bazel-review.googlesource.com/#/c/3170
MOS_MIGRATED_REVID=118587980
|
|
|
|
|
|
|
|
|
|
| |
In this way, we prevent the experimental UI from reporting
about the number of actions (actually 0) currently running.
--
Change-Id: Ic1c02d388f1928b8fe8d2d66dc14757b0213c43b
Reviewed-on: https://bazel-review.googlesource.com/#/c/3180
MOS_MIGRATED_REVID=118580580
|
|
|
|
|
|
|
|
| |
If a load statement is present in the WORKSPACE file, the
workspace name attribute will be lost from the WORKSPACE file.
--
MOS_MIGRATED_REVID=118577315
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118565877
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118560010
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bazel clean never runs any actions, hence any message
about running actions would confuse the user. Therefore,
signal that clean is a non-building command so that the
experimental UI knows not the report about progress of
building.
--
Change-Id: I193f199b052e990992359bc9efdbe34db397ac5f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3125
MOS_MIGRATED_REVID=118554435
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118500217
|
|
|
|
|
|
|
| |
those modules already contain all the headers that are needed.
--
MOS_MIGRATED_REVID=118457691
|
|
|
|
|
|
|
| |
looking up actions registered from Aspects that use a non-empty AspectParameters.
--
MOS_MIGRATED_REVID=118455180
|
|
|
|
|
|
|
| |
non-keep-going build. Setting errorDepKey was only mostly harmless, to mix memes. (Actually, it was quite harmful.)
--
MOS_MIGRATED_REVID=118410594
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118383557
|
|
|
|
|
|
|
|
|
| |
encountered during a build
Currently when evaluating a file or symlink leading to an external mutable object, Blaze throws an exception with unclear messages. The message does not contain the actual path but rather [/]/[] instead. This change updates FileFunction to allow bubbling up the error with the accurate path.
--
MOS_MIGRATED_REVID=118381323
|
|
|
|
|
|
|
| |
instead of DefaultSubject.
--
MOS_MIGRATED_REVID=118261285
|
|
|
|
|
|
|
| |
we could get an NPE if one initializes a data structure the other uses. Also delete an unused field and do a small visibility drive-by.
--
MOS_MIGRATED_REVID=118248373
|
|
|
|
| |
MOS_MIGRATED_REVID=118246740
|
|
|
|
|
|
|
| |
can trigger on it.
--
MOS_MIGRATED_REVID=118234431
|
|
|
|
|
|
|
|
|
|
|
| |
repository.download function now creates the necessary directories before
downloading.
Fixes #1069
Fixes #1078
--
MOS_MIGRATED_REVID=118026986
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will tell the experimental UI not to produce updates on the
build status and also pass through correctly STDOUT/STDERR events.
In particular, the standard output is suitable for consumption by
other tools.
--
Change-Id: Ifffd445433a29df20f062a762fe6280229319196
Reviewed-on: https://bazel-review.googlesource.com/#/c/3123
MOS_MIGRATED_REVID=118024251
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117968196
|
|
|
|
|
|
|
| |
that keeps the Strings and creates the corresponding Value objects only at expansion time.
--
MOS_MIGRATED_REVID=117947058
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117939121
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, during build, STDOUT and STDERR events
are reported as separate events, properly terminated by CR LF.
After the completion of the build, however, STDOUT and STDERR
are passed through byte by byte, to allow nicely formatted output.
Info commands, however, do not build, so there is no event to signal
end of build; hence report that fact directly to the UI.
--
Change-Id: Ic236d33ee6e65637016370e15ed37e3d9494a258
Reviewed-on: https://bazel-review.googlesource.com/#/c/3122
MOS_MIGRATED_REVID=117934742
|
|
|
|
|
|
|
|
| |
The previous implementation was hiding errors from before a load
statement as a result of the workspace split.
--
MOS_MIGRATED_REVID=117933781
|
|
|
|
|
|
|
| |
They are automatically added when printing the error message.
--
MOS_MIGRATED_REVID=117927312
|
|
|
|
|
|
|
|
| |
This is one of the last pieces of state in BlazeRuntime that isn't safe to
share across command invocations.
--
MOS_MIGRATED_REVID=117910631
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The client provides information about whether the terminal is a tty, and
which width the output should be formatted for. Passing this information
as explicit command-line arguments has the disadvantage that it overrides
any setting in configuration files. While usually there is no one-size-fits-all
value for terminal width, it doesn't make sense either to have an option
where the user cannot set a default. Fix this by providing the client options
as least imported rc-source.
--
Change-Id: Iad9eddbb3ff1777f4b423053e21aeac9fd7c466f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3092
MOS_MIGRATED_REVID=117833645
|
|
|
|
|
|
|
|
|
|
|
| |
When specifying which command names to parse options for, given the
command annotation, ensure that "common" comes first, so that it can
be overridden by more specific options.
--
Change-Id: I20cd90c098e993580c32297d1e36c8a6c939873a
Reviewed-on: https://bazel-review.googlesource.com/#/c/3091
MOS_MIGRATED_REVID=117821257
|
|
|
|
|
|
|
|
|
| |
Windows.
Progress towards #930.
--
MOS_MIGRATED_REVID=117799006
|
|
|
|
|
|
|
|
|
| |
Use -p when mkdir, create the server directory in the
temporary directory and ensure we delete the server directory
on the tear_down.
--
MOS_MIGRATED_REVID=117728350
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example, if you have a BUILD file that does:
load('@foo//bar:baz.bzl', 'my_rule')
my_rule(...)
If baz.bzl uses Label('//whatever'), this change makes //whatever resolve to
@foo//whatever. Previous to this change, it would be resolved to the repository
the BUILD file using my_rule was in.
RELNOTES[INC]: Labels in .bzl files in remote repositories will be resolved
relative to their repository (instead of the repository the Skylark rule is
used in).
--
MOS_MIGRATED_REVID=117720181
|
|
|
|
|
|
|
|
|
| |
Without that spaces, we were getting:
src/test/shell/bazel/external_integration_test: line 540: [: missing `]'
in the test log.
--
MOS_MIGRATED_REVID=117707546
|
|
|
|
|
|
|
|
|
| |
Fixes #1041
RELNOTES: Add repository_ctx.download and repository_ctx.download_and_extract function.
--
MOS_MIGRATED_REVID=117698142
|
|
|
|
|
|
|
|
|
| |
basically doing the same thing with it.
This simplifies the code and avoids unnecessary re-wrapping, which saves memory.
--
MOS_MIGRATED_REVID=117693050
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks the query command
*** Original change description ***
Update the java_langtools flag to default to @bazel_tools//tools/jdk:langtools.
--
MOS_MIGRATED_REVID=117588472
|