| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
Now users can point to default Java tool jars in custmized
java_toolchain rule defined in project's BUILD file.
--
Change-Id: I064c9646e8681a3f5669d7163b1b3cb5cc0b16b7
Reviewed-on: https://cr.bazel.build/9250
PiperOrigin-RevId: 151422924
MOS_MIGRATED_REVID=151422924
|
|
|
|
|
|
|
|
| |
--
Change-Id: Ic1632229e67bf82b69983f9614258c5fd54c12d8
Reviewed-on: https://cr.bazel.build/9390
PiperOrigin-RevId: 151422502
MOS_MIGRATED_REVID=151422502
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed: https://github.com/bazelbuild/bazel/issues/2666
See: https://github.com/bazelbuild/bazel/issues/2726
RELNOTES: Windows MSVC wrappers: Not filtering warning messages anymore, use --copt=-w and --host_copt=-w to suppress them.
--
PiperOrigin-RevId: 151422047
MOS_MIGRATED_REVID=151422047
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151407958
MOS_MIGRATED_REVID=151407958
|
|
|
|
|
|
|
|
| |
RELNOTES: All android_binarys are now signed with both Apk Signature V1 and V2. See https://source.android.com/security/apksigning/v2.html for more details.
--
PiperOrigin-RevId: 151404899
MOS_MIGRATED_REVID=151404899
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151383588
MOS_MIGRATED_REVID=151383588
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151381769
MOS_MIGRATED_REVID=151381769
|
|
|
|
|
|
|
|
|
|
| |
e.g.: cmd = "$(CC) foo.cc > $@"
Fixes #2729
--
PiperOrigin-RevId: 151369889
MOS_MIGRATED_REVID=151369889
|
|
|
|
|
|
|
|
|
|
|
|
| |
...irrespective of their success status. While a build typically
contains too many successful actions to report them all, extra actions
included in a build are worth reporting.
--
Change-Id: I6b20935895aa7b16836d6271f456176a7113317e
Reviewed-on: https://cr.bazel.build/9519
PiperOrigin-RevId: 151328633
MOS_MIGRATED_REVID=151328633
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the rule.
Example:
tools/newlang/BUILD:
toolchain_type(name = "toolchain_type")
Allows users to refer to //tools/newlang:toolchain_type when discussing the
newlang toolchain.
The previous usage:
tools/newlang/BUILD:
toolchain_lookup(name = "lookup")
Lead to labels like //tools/newlang:lookup, which was unclear that each
language's toolchain needs one unique instance of toolchain_(lookup|type).
--
PiperOrigin-RevId: 151326827
MOS_MIGRATED_REVID=151326827
|
|
|
|
|
|
|
|
|
| |
Some policies can come from the module API, and some come from the user via
startup argument. Clarify which one is which.
--
PiperOrigin-RevId: 151324618
MOS_MIGRATED_REVID=151324618
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151322384
MOS_MIGRATED_REVID=151322384
|
|
|
|
| |
Change-Id: Ifc30d7a2f1cd698f563342e41be9f59989af871b
|
|
|
|
|
|
|
|
| |
three files
--
PiperOrigin-RevId: 151319959
MOS_MIGRATED_REVID=151319959
|
|
|
|
|
|
|
|
| |
http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/lastCompletedBuild/testReport/(root)/(empty)/test_sandbox_mount_customized_path/
--
PiperOrigin-RevId: 151306949
MOS_MIGRATED_REVID=151306949
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151302544
MOS_MIGRATED_REVID=151302544
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151302418
MOS_MIGRATED_REVID=151302418
|
|
|
|
|
|
|
|
|
|
| |
This only add the bootstrap tests. We could add more tests but we should probably rather just update the 15.10 VMs to run Ubuntu 16.04.
Tracking issue #2741.
--
PiperOrigin-RevId: 151299465
MOS_MIGRATED_REVID=151299465
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151297803
MOS_MIGRATED_REVID=151297803
|
|
|
|
|
|
|
|
|
|
| |
- Adjust the date for the milestones
- Move items that we are completing earlier and set P0 for 0.6
- Some other rewriting
--
PiperOrigin-RevId: 151296351
MOS_MIGRATED_REVID=151296351
|
|
|
|
|
|
|
|
|
|
|
|
| |
Additionally to reporting on the originally received command line, also report
it in a parsed form. This, in particular, includes reconstructing the options
originally provided by the user.
--
Change-Id: I5a1c6ed57874f1d37d10bf11d597256d63bc5516
Reviewed-on: https://cr.bazel.build/9459
PiperOrigin-RevId: 151288656
MOS_MIGRATED_REVID=151288656
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151263526
MOS_MIGRATED_REVID=151263526
|
|
|
|
|
|
|
|
| |
RELNOTES: n/a
--
PiperOrigin-RevId: 151203625
MOS_MIGRATED_REVID=151203625
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151201374
MOS_MIGRATED_REVID=151201374
|
|
|
|
|
|
|
|
|
| |
This has no effect unless --incremental_dexing is used.
RELNOTES: turn on --experimental_incremental_dexing_error_on_missed_jars by default.
--
PiperOrigin-RevId: 151198031
MOS_MIGRATED_REVID=151198031
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151193034
MOS_MIGRATED_REVID=151193034
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151183770
MOS_MIGRATED_REVID=151183770
|
|
|
|
|
|
|
|
|
|
|
| |
The linux-sandbox no longer requires extensive configuration via flags,
so the command-line arguments will easily fit into the allowed length.
This simplifies the code and gets rid of some I/O.
--
PiperOrigin-RevId: 151176551
MOS_MIGRATED_REVID=151176551
|
|
|
|
|
|
|
|
|
|
|
| |
Extract the process-wrapper + symlink tree sandbox strategy into its own
class and allow its use in FreeBSD.
RELNOTES: Bazel can now use the process-wrapper + symlink tree based sandbox implementation in FreeBSD.
--
PiperOrigin-RevId: 151171652
MOS_MIGRATED_REVID=151171652
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151170448
MOS_MIGRATED_REVID=151170448
|
|
|
|
|
|
|
|
|
|
| |
This allows us to see for example whether an action ran using the
"process wrapper + symlink tree" sandbox or the real "PID and mount
namespaces" Linux sandbox.
--
PiperOrigin-RevId: 151165170
MOS_MIGRATED_REVID=151165170
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151160662
MOS_MIGRATED_REVID=151160662
|
|
|
|
|
|
|
|
|
|
| |
into a separate method, so that the main becomes shorter. Also move most of the code in main to an instance method.
RELNOTES: n/a
--
PiperOrigin-RevId: 151155142
MOS_MIGRATED_REVID=151155142
|
|
|
|
|
|
|
|
|
|
| |
The header mapping used to be generated by J2ObjcTranspilationAction and consumed by dependent J2ObjcTranspilationActions. This setup led to chained J2ObjcTranspilationActions and long critical path build time. With GenerateJ2objcHeaderMap action, we break that chain and shorten the critical path build time.
This feature is guarded behind a new build flag, --experimental_j2objc_header_map.
--
PiperOrigin-RevId: 151149906
MOS_MIGRATED_REVID=151149906
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151145409
MOS_MIGRATED_REVID=151145409
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151141112
MOS_MIGRATED_REVID=151141112
|
|
|
|
|
|
|
|
|
|
|
| |
Note that this is not quite a no-op. Setting -isystem puts these directories at
the beginning of the search list, whereas not setting them results in them
being near the end. However, this code is unnecessary and confusing and caused
a bug with the clang toolchains so it is best to remove it.
--
PiperOrigin-RevId: 151140445
MOS_MIGRATED_REVID=151140445
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
execution.
If you're feeling like you've already seen this, that's correct, these were the exact contents of commit e860316559eac366d47923a8eb4b5489a661aa35... and then, on Nov 15, something unclear happened and the code disappeared! Perhaps it was the result of a faulty sync. In any case, nobody noticed, and the CL went in. It was later rolloed back and resubmitted, but the crucial code changes were gone.
TESTED=local server with profiling for SHA1 specifically
RELNOTES: n/a
--
PiperOrigin-RevId: 151139685
MOS_MIGRATED_REVID=151139685
|
|
|
|
|
|
|
|
|
|
| |
Previously the mapping is generated directly by J2ObjC through j2objc_wrapper.py.
RELNOTES:None.
--
PiperOrigin-RevId: 151138711
MOS_MIGRATED_REVID=151138711
|
|
|
|
|
|
|
|
|
|
| |
signaledDeps field directly in InMemoryNodeEntry.
Should save ~24 bytes per freshly evaluating node entry (I haven't calculated object alignment for InMemoryNodeEntry now, so could be more or less). Also might save some memory for re-evaluating node entries, since the BuildingState class had to be padded out to a multiple of 8 bytes before the DirtyBuildingState fields could start. Don't actually know if that was happening.
--
PiperOrigin-RevId: 151138224
MOS_MIGRATED_REVID=151138224
|
|
|
|
|
|
|
|
| |
case-insensitive paths.
--
PiperOrigin-RevId: 151137308
MOS_MIGRATED_REVID=151137308
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151130566
MOS_MIGRATED_REVID=151130566
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151129669
MOS_MIGRATED_REVID=151129669
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rollback of commit df366408188f0451bae9b2ed079c795a4beb2e2b.
In addition to undoing the rollback of my previous change, fix the bugs it
introduced and add tests for those bugs.
Always ignore empty filters. Empty filters are always useless or
counterproductive. Before the original change, empty filters as a single item
within the list of filters (e.g., ["en", ""]) were ignored, but empty filters
as a portion of a string in the list (e.g., ["en,"]) were not. I can't imagine
any reason people would actually want the empty filter (if it were handled
correctly, it would effectively tell Bazel to just ignore every other filter
the user passed in).
Since it makes more sense with the new code, represent the stringified filters
as a list of strings, rather than a single string of comma-seperated values.
Manually trim whitespace from each token. Before the original change, the code
trimmed whitespace following commas (e.g., ["en, es"] -> ["en,es"]) but not
otherwise. If we're allowing whitespace in filter strings anyway, there doesn't
seem to be any reason to allow it in some places but not others.
--
PiperOrigin-RevId: 151128685
MOS_MIGRATED_REVID=151128685
|
|
|
|
|
|
|
|
|
|
|
| |
If needed you can restore the old behavior by passing the flag
--sandbox_tmpfs_path=/tmp to bazel.
Fixes #2508.
--
PiperOrigin-RevId: 151127924
MOS_MIGRATED_REVID=151127924
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also refactor the way we compute writable dirs so that they're computed
only once per running action, not twice.
Fixes #2056, fixes #1973, fixes #1460.
RELNOTES: /tmp and /dev/shm are now writable by default inside the
Linux sandbox.
--
PiperOrigin-RevId: 151123543
MOS_MIGRATED_REVID=151123543
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Abusing the checkEnvironment method, register early on the event bus
and catch all events till the time we are supposed to process the options.
This solves the problem that events relevant to the build event stream are
posted (e.g., the GotOptions event) before(!) we know if a BuildEventStreamer
is required.
--
Change-Id: Iac63302351b862772638791932bcaa58b60b22fb
Reviewed-on: https://cr.bazel.build/9457
PiperOrigin-RevId: 151123359
MOS_MIGRATED_REVID=151123359
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 151120717
MOS_MIGRATED_REVID=151120717
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of trying to detect overlapping mount points, just ignore any
ENOENT errors during remount. If this error happens, the mount point
wouldn't be accessible anyway, so there's no harm if the remount fails.
Fixes #1948.
--
PiperOrigin-RevId: 151118726
MOS_MIGRATED_REVID=151118726
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Try to run /bin/true as a test of whether the Linux sandbox works,
instead of just trying to create a bunch of namespaces as a proxy.
This helps resolve issues on Linux distros where the earlier check
worked, but then the sandbox ultimately failed due to other operations
being unsupported.
As an example, Debian Jessie and certain Docker versions seem to allow
the creation of PID namespaces, but forbid mounting a new proc on top of
/proc (see #1972). This resulted in Bazel thinking that sandboxing works
fine, when it actually didn't. The improved check correctly catches this
situation and disabled sandboxing.
--
PiperOrigin-RevId: 151116894
MOS_MIGRATED_REVID=151116894
|