| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
ControlFlowChecker has a precondition check that assumes nested functions do not occur. While this assumption is reasonable for a valid Skylark syntax, linter can actually be invoked on malformed files and users would get a stack trace instead of a human-readable linter error.
Alternative and possibly a better strategy would to not run CFChecker in case parse errors are detected.
fixes #4511
Closes #4512.
PiperOrigin-RevId: 185538897
|
|
|
|
| |
PiperOrigin-RevId: 183840991
|
|
|
|
|
| |
Change-Id: I33717f6a68035bfd5f8406685f935253e1d24325
PiperOrigin-RevId: 183815476
|
|
|
|
|
|
|
|
|
|
|
| |
The debian package changlog file doesn't have to contain the real CHANGELOG.md.
Parsing change log is error-prone and caused our release job to fail everytime,
so here we simplified the script for generating changelog.
Fix https://github.com/bazelbuild/bazel/issues/4530
Change-Id: I8adc5a98def5709ea57f9edbed9f0cf772a48d76
PiperOrigin-RevId: 183651058
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We'll just replace them with either native support for running tests inside
Docker containers on CI or with VMs running the operating system.
This gets rid of the "let's download 8 GB of Docker images" step when running
`bazel build //...`.
RELNOTES: None.
Closes #4506.
PiperOrigin-RevId: 183078052
|
|
|
|
|
| |
Change-Id: Ie6070b01e7d004589064edc1f182baa6b6fac8b4
PiperOrigin-RevId: 182940613
|
|
|
|
|
|
|
| |
...as it breaks shell tests
Change-Id: I191ec7c0f36832ff064af0b756a8c8fb41eb2a87
PiperOrigin-RevId: 182509548
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added tests for checking JavaExportsProvider state.
Refactored logic working with collection in favor of using Streams to improve readability.
All other providers will be implemented in next CLs.
previous CL with JavaCompilationArgsProvider implementation is https://github.com/bazelbuild/bazel/commit/32dff21d00ad7d1bdf50e8761d675a6e7e002de9,
JavaSourceJarsProvider : https://github.com/bazelbuild/bazel/commit/5bd53cb609480ca896ca2d011f415b424c63ce63
RELNOTES:none
PiperOrigin-RevId: 182342490
|
|
|
|
| |
Change-Id: I05fa85967317c4581081adfc620e24a7c6322669
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1.Deleted config_setting for --cpu=x64_windows_msys, because we don't build
Bazel with MSYS gcc anymore.
2.Deleted config_setting for --cpu=x64_windows_msvc, because it uses exactly
the same toolchain as --cpu=x64_windows, it'll be removed in the future.
This change reduces the complexity of our BUILD files and make them less
confusing.
Change-Id: I939831a6861413b0f745fb1be98aacd4fb780e0a
PiperOrigin-RevId: 181751853
|
|
|
|
|
|
|
|
| |
Fixes #3872
Closes #3873.
PiperOrigin-RevId: 181644101
|
|
|
|
|
|
|
|
| |
...until the bugs in the google_compute_engine scripts are fixed
upstream.
Change-Id: I3fcced5ad82735270c991f5a3595b34da60de544
PiperOrigin-RevId: 181158629
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
FreeBSD should work again, so re-enable it.
*** Original change description ***
Remove FreeBSD from our CI temporarily.
RELNOTES: None.
PiperOrigin-RevId: 181140165
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 180857355
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 180851611
|
|
|
|
|
| |
Change-Id: Ie355e9f122c074b24d119438e1f0a6e75300d1d1
PiperOrigin-RevId: 179043273
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Argument mixes string and array. Use * or separate argument.
- Quote the grep pattern so the shell won't interpret it.
- Use "${var:?}" to ensure this never expands to /* .
- > is for string comparisons. Use -gt instead.
- Quote the parameter to -name so the shell won't interpret it.
Closes #4163.
PiperOrigin-RevId: 179042046
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 178892596
|
|
|
|
|
|
|
|
|
| |
passes.
Fixes #4268 .
RELNOTES: None.
PiperOrigin-RevId: 178604877
|
|
|
|
|
|
|
|
| |
This is because I want to add another remote execution related tool, the remote_client, which will use the Remote Execution API to fetch blobs from a remote cache. I will use this tool as part of end-to-end tests for remote execution.
TESTED=remote integration tests, presubmit
RELNOTES: None
PiperOrigin-RevId: 177995895
|
|
|
|
|
|
|
|
|
| |
...through the corresponding environment variables. In this
way, more than one documentation version can be served, e.g.,
to simplify comparing.
Change-Id: I4ae069a4a48f12e9bd48210ee3bd22299149f59d
PiperOrigin-RevId: 177959891
|
|
|
|
|
|
|
| |
This will enable an easier transition from checked-in BUILD files to ones generated by copybara.
RELNOTES: None
PiperOrigin-RevId: 177514519
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the following error I got when building from scratch on Raspbian:
```
src/main/protobuf/invocation_policy.proto: File not found.
src/main/protobuf/command_line.proto: File not found.
```
Note:
```
protoc --version
libprotoc 3.0.0
```
Closes #4187.
PiperOrigin-RevId: 177306773
|
|
|
|
|
|
|
|
|
|
| |
ibazel implements a the same command line interface as bazel, so we can just use the same completion function.
See https://github.com/bazelbuild/bazel-watcher.
Closes #4091.
PiperOrigin-RevId: 177282217
|
|
|
|
|
|
|
|
| |
see #4023
Closes #4051.
PiperOrigin-RevId: 177279457
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently powershell on macOS is a thing now...
However, chocolatey does not yet seem to be...
cc @dslomov
Closes #4026.
PiperOrigin-RevId: 177172660
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The test case test_failed_actions_with_keep_going was never correct
and only worked by accident: it relied on bazel starting at least
two actions, if for there are at least two where all the dependencies
are already met; however bazel is clever and analyzes the resources
of the system it is running in, and if they are small will only run one
genrule at a time. Fix this by telling it to run 2 actions and lying
about the available resources of the local system.
Also increase the test size and reenable the test for remote execution.
Fixes #3995.
Change-Id: Ic84de17a98a2e74c24901d4efb38d7631de4690a
PiperOrigin-RevId: 176511026
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is applying the version 1.1 of the specification (https://reproducible-builds.org/specs/source-date-epoch/)
where the only timestamp that Bazel puts in the final targets is overridden by the value of SOURCE_DATE_EPOCH.
This change also remove the legacy SOURCE_DATE_EPOCH handling which wasn't really following
the spec.
Note that Bazel itself tries hard to remove all timestamps from intermediary binaries and
overridde SOURCE_DATE_EPOCH in most action, which is a not according to the version 1.0 of the spec
but according to the expected change for version 1.1.
RELNOTES: SOURCE_DATE_EPOCH (https://reproducible-builds.org/specs/source-date-epoch/) can
be used to override the timestamp used for stamped target (when using --stamp).
Fixes #2240.
Change-Id: I074e7905fa6745cc706f7391340aeae9188909ca
PiperOrigin-RevId: 176489717
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/3761
Closes #4015.
PiperOrigin-RevId: 176340908
|
|
|
|
|
| |
Change-Id: I9ae0c56844db45e28eb5a08e8180514aa2729fdf
PiperOrigin-RevId: 176114077
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/75d8fe1d347b45f4dd808a76c3a73b24f9728284.
RELNOTES: None
PiperOrigin-RevId: 176107565
|
|
|
|
| |
Change-Id: I9ae0c56844db45e28eb5a08e8180514aa2729fdf
|
|
|
|
|
|
| |
This test is hitting time out on remote execution. Until the workers are fixed, deactivate it.
PiperOrigin-RevId: 175478669
|
|
|
|
|
|
| |
Issue bazelbuild/continuous-integration#149: FreeBSD 12 slaves cannot copy the Bazel binary keeping permission correctly.
PiperOrigin-RevId: 175474382
|
|
|
|
|
|
|
|
|
| |
unlike earlier versions,
openjdk9 returns "javac 9" when asked for its version
Closes #4004.
PiperOrigin-RevId: 175029317
|
|
|
|
|
|
|
| |
This is now done by a Google Cloud Container Builder job.
Change-Id: I33a9543f9b5bdb083171482e9eaebdb43e77181b
PiperOrigin-RevId: 174905217
|
|
|
|
|
|
| |
This target was removed.
PiperOrigin-RevId: 174870373
|
|
|
|
| |
PiperOrigin-RevId: 174867981
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using `bazel build //site` will now build the site (needs the proper
version of Jekyll in the path :/), `bazel run //site` will serve it
using Jekyll.
This change also contains the yaml file to build and deploy the
site on Google Cloud Container Builder. This will allow to remove
that special hook from our CI.
Note: this is copied from https://github.com/bazelbuild/bazel-blog
Change-Id: I6bb04fea0fa80623bd5d25a5f191ae49e8074e92
PiperOrigin-RevId: 174459256
|
|
|
|
|
|
| |
This is no longer maintained and the CI is turned down.
PiperOrigin-RevId: 174456265
|
|
|
|
|
|
|
|
|
|
|
| |
- Migrate bazel-tests-remote.json file from
bazelbuild/continuous-integration repo to bazelbuild/bazel repo.
- Update toolchain and configs to use container v0.2.0 and new
configs (v0.7.0 for c++, v0.6.0 for java).
Change-Id: Ib376f662c6c6cec617d82133254f9a12ef67e748
PiperOrigin-RevId: 174329569
|
|
|
|
|
|
|
| |
Unicode characters are trouble we do not want.
Change-Id: I5f5239baab60a875a697f2ee3104225e19c0ce1d
PiperOrigin-RevId: 173245285
|
|
|
|
|
|
|
|
|
|
| |
Now that the experimental_ui is enabled by default in commit
784bb52613feb484221c3aa6756de, we do not need to enable it in the
(recommended) bazelrc file anymore. While there, also move the default
number of actions shown in the experimental_ui to the flag default.
Change-Id: I74673a0d677b6d832c9fb5e2983f97c0dcbc44e4
PiperOrigin-RevId: 172736977
|
|
|
|
|
| |
Change-Id: I5e946c093499dffd0a34253a5f8e47c49c6a12ec
PiperOrigin-RevId: 172686697
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous regex was only matching lines and was not even correctly
doing so. We no match everything that is starting with none, n/a or
no as a sentence or as a full line. We also match empty string and
'.' as a full line.
RELNOTES: .
RELNOTES: None.
RELNOTES: No.
Change-Id: I6e85627170ce35e652c90a37e735b7db93c88b4e
PiperOrigin-RevId: 172452278
|
|
|
|
|
|
|
|
|
|
| |
Because the empty list was returned for the list of hashes to ignore,
we matching all the lines in the following grep. By adding a dummy
hashes, it ensure that list is never empty and we thus never
give a match all pattern.
Change-Id: Ic5446c16b56633805e61b24ad71b67029a7b01e3
PiperOrigin-RevId: 172321625
|
|
|
|
|
|
|
|
| |
- Avoid trap being called when grep is not matching (|| true)
- Ensure we always start in master branch
Change-Id: I7a71abbdfae7dc2b9680e769ed0322a6a12221dc
PiperOrigin-RevId: 172316454
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If an absolute javabase is desired, the following set of rules can be used:
java_runtime_suite(name="suite", default=":runtime")
java_runtime(name="runtime", java_home=<path to the JDK>)
Then --javabase can be pointed to the java_runtime_suite() rule.
Alternatively, the java_runtime rule can reference a Make variable:
java_runtime(name="runtime", java_home="$(ABSOLUTE_JAVABASE)")
Then the Javabase can be specified on the command line like this:
--javabase=<your package>:suite --define=ABSOLUTE_JAVABASE=<path to the JDK>
RELNOTES[INC]: --javabase=<absolute path> and --host_javabase=<absolute path>
are not supported anymore. If you need this functionality java_runtime_suite(name="suite", default=":runtime") java_runtime(name="runtime", java_home=<path to the JDK>) is an alternative.
PiperOrigin-RevId: 171798416
|
|
|
|
|
| |
RELNOTES: No. (test)
PiperOrigin-RevId: 171673073
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this commit:
* buildenv.sh: restore its state to that as of
commit 511c35b46cead500d4e76706e0a709e50995ceba
* CommonCommandOptions.java: remove a deprecated
no-op flag
* WindowsPathFragment.java: implement an
ASCII-only isLetter function, use that instead
of Character.isLetter, because the latter
returns true for some Unicode characters too
* bazel_bootstrap_distfile_test: remove logging
that we no longer need, since the bugfix for
issue #3618 will be pushed to GitHub later today
Change-Id: Ibda70219e974f0c47bc82addc647d8951f4bd701
PiperOrigin-RevId: 171498977
|