| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 194284174
|
|
|
|
|
|
|
|
| |
We accidentally removed the .deb file, even though it's supposed to be uploaded and we didn't remove the .sig/.sha256 files of the artifacts that are *not* supposed to be uploaded.
This change fixes that.
PiperOrigin-RevId: 193651950
|
|
|
|
|
|
|
|
| |
These are the scripts I'm currently using for the Bazel 0.12.0 release.
Closes #4908.
PiperOrigin-RevId: 190598268
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 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
|
|
|
|
|
|
|
| |
This is now done by a Google Cloud Container Builder job.
Change-Id: I33a9543f9b5bdb083171482e9eaebdb43e77181b
PiperOrigin-RevId: 174905217
|
|
|
|
|
|
| |
This target was removed.
PiperOrigin-RevId: 174870373
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
This URL works everywhere in the world and is easier to remember.
It also allow us to change the backend transparently.
Change-Id: I25ed753e5a4c27f26a8a1a86266cc06a3cf22744
PiperOrigin-RevId: 170789151
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add recursive test_suite rules for all tests that
ci.bazel.io runs for Windows, and set the
top-level test_suite as the CI test target.
Doing so shortens the command line and works
around https://github.com/bazelbuild/bazel/issues/3742
I verified that the old set of tests are the same
as the new set.
Change-Id: Id8d5da3f0c03c9b8969a9f8e1e9a3096888365aa
PiperOrigin-RevId: 169242858
|
|
|
|
|
|
|
|
|
| |
We were having 2 level of parameters, so we had
a unused parameters called "parameters".
Fixes #3704.
PiperOrigin-RevId: 167982900
|
|
|
|
|
|
|
|
| |
So we do not execute more tests that needed.
Issue #3704.
PiperOrigin-RevId: 167976313
|
|
|
|
|
|
| |
Fixes #3703.
PiperOrigin-RevId: 167973195
|
|
|
|
|
|
|
|
|
| |
Now every test labelled slow will be moved to that job.
Issue bazelbuild/continuous-integration#98.
Change-Id: I37baa0f4233201557493a8fac643e571026fcd93
PiperOrigin-RevId: 167854935
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To select which test to run on bazel-docker-tests, use
the docker and shard- tag intead of hard to read queries and
shard based on the compilation mode.
Also copy the file to bazel-slow-tests in prevision from
renaming the job on CI.
Issue bazelbuild/continuous-integration#98.
Change-Id: Ie8e9a21c5a1ce93c9ecaa74cbb2734c150c7f592
PiperOrigin-RevId: 167752261
|
|
|
|
|
|
|
| |
Remove optional variation and simplify node specifications.
Change-Id: Ie0a137768312152d9c036a94e5214b419b3c12ce
PiperOrigin-RevId: 167717139
|
|
|
|
|
| |
Change-Id: If2bf41a96cde21bb97017d4fa35f8f61111635a1
PiperOrigin-RevId: 167714075
|
|
|
|
|
|
|
|
|
| |
So release are build with -c opt
Fixes #3340.
Change-Id: I455b5c2a53be5fb8fb39e247a849058f19d1d884
PiperOrigin-RevId: 167266776
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 167132537
|
|
|
|
|
|
|
| |
This flag no longer exists after MSVC-less CROSSTOOL became default.
Change-Id: I015c3c03c72d15c0efe00f48e923a2d54876b1b2
PiperOrigin-RevId: 166680678
|
|
|
|
|
|
|
|
|
|
|
| |
...and re-enable of FreeBSD. It turns out that the timeout-flakyness
was just because the CI machines weren't fast enough. Running the test
150 times showed no further timeout.
Fixes #3614.
Change-Id: Icdf2f91b1fe91e22117c3cf6d3fda9409d473198
PiperOrigin-RevId: 166470850
|
|
|
|
|
|
|
|
| |
This divide the docker tests in 2 parts (with the current build file it is 6 per jobs) and each configuration can now be run on different worker.
Issue bazelbuild/continuous-integration#98
PiperOrigin-RevId: 166469254
|
|
|
|
|
|
| |
This test is timeout flaky, deactivating.
PiperOrigin-RevId: 166180421
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
osx_cc_wrapper.sh was not working correctly in cases when multiple
rpaths were specified on linking command line. This cl modifies the
wrapper to record all rpaths, and use the rpath that corresponds to a particular
library when updating libraries install name.
Fixes #3450
RELNOTES: None.
Change-Id: I614694a792b6724a1db9814ee25af1802560c463
PiperOrigin-RevId: 165618946
|
|
|
|
|
|
|
|
|
| |
By replacing uses of /bin/bash by /bin/sh, a tool which is more
reliably at this location. Then, enable most of the bazel tests
for FreeBSD as well.
Change-Id: Ic56a1705858f1ed67d1e96e2937e9389dd1d0e36
PiperOrigin-RevId: 164241635
|
|
|
|
|
|
|
| |
Instead just using a //examples/cpp:hello-world to make sure the MSYS toolchain doesn't regress.
RELNOTES: None
PiperOrigin-RevId: 163676783
|
|
|
|
|
|
|
| |
Trailing commas are not part of the JSON specification.
Change-Id: Icbfc072b448e422a3cdb7fd827fbfb392611d344
PiperOrigin-RevId: 163331760
|
|
|
|
| |
PiperOrigin-RevId: 163326705
|
|
|
|
|
|
|
| |
This code was replaced by code on the CI side where it belongs.
Change-Id: I67741f27aee5f133fe29f8e1d57b843d96f3f9ea
PiperOrigin-RevId: 163320045
|
|
|
|
|
|
|
|
|
|
| |
This will allow to update the file that explains how to build
and test Bazel at the same time that Bazel evolves.
Fixes bazelbuild/continuous-integration#99
Change-Id: I2ab8641a6eb5d8cf7ea95667bd6b3af42be5a420
PiperOrigin-RevId: 163320005
|
|
|
|
|
|
|
| |
To be cherry-picked for #3375
Change-Id: I81e3660d1e01935101a19d75e1a696296df1941d
PiperOrigin-RevId: 163202698
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Now the new jenkins pipeline has been rolled forward we actually needs that change
To cherry-pick for #3375
*** Original change description ***
Automated rollback of commit 6d6e87297fe8818e4c374fdfabfbcf538bca898a.
*** Reason for rollback ***
Does not work so well, see https://storage.googleapis.com/bazel/0.5.3/rc1/index.html
*** Original change description ***
Release script: generate the index.html from the commit message
Do not rely on the README.md anymore, because it relies on log
still existing forever on Jenkins. Incoming change will just provides
the log as a file that will be archived on GCS.
PiperOrigin-RevId: 162950464
|
|
|
|
|
|
|
| |
This is the first CL to remove MSYS Bazel.
RELNOTES:
PiperOrigin-RevId: 162731750
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Does not work so well, see https://storage.googleapis.com/bazel/0.5.3/rc1/index.html
*** Original change description ***
Release script: generate the index.html from the commit message
Do not rely on the README.md anymore, because it relies on log
still existing forever on Jenkins. Incoming change will just provides
the log as a file that will be archived on GCS.
Change-Id: Ib962c249145d222bf9909070698c5d419b34db4c
PiperOrigin-RevId: 162321172
|
|
|
|
|
|
|
|
|
| |
Do not rely on the README.md anymore, because it relies on log
still existing forever on Jenkins. Incoming change will just provides
the log as a file that will be archived on GCS.
Change-Id: Ib962c249145d222bf9909070698c5d419b34db4c
PiperOrigin-RevId: 161804017
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 160482939
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on output of static analysis tool.
https://github.com/koalaman/shellcheck/wiki/SC2166
https://github.com/koalaman/shellcheck/wiki/SC2207
https://github.com/koalaman/shellcheck/wiki/SC2145
https://github.com/koalaman/shellcheck/wiki/SC2001
https://github.com/koalaman/shellcheck/wiki/SC2129
https://github.com/koalaman/shellcheck/wiki/SC2128
https://github.com/koalaman/shellcheck/wiki/SC2004
https://github.com/koalaman/shellcheck/wiki/SC2048
Closes #3162.
PiperOrigin-RevId: 160261247
|
|
|
|
|
|
|
|
|
|
| |
Double quoting make bash interpret the backquote and bazel is not
on the path of the resulting process, showing error on the console.
To cherry-pick for #3086.
Change-Id: I15a4cdbd349300c87bd90d56ecb8df63ecf62dfb
PiperOrigin-RevId: 160250275
|
|
|
|
|
|
|
| |
To cherry-pick for #3086.
Change-Id: I05db2aef04a7cd6cec22c918f00e4b47bae3a1f4
PiperOrigin-RevId: 160249482
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will help diagnose
https://github.com/bazelbuild/bazel/issues/2977,
which I believed to have been fixed by the release
of 0.5.0, however it seems to have failed once
more with 0.5.0, alas without knowing the actual
bootstrap bazel's version I cannot be sure.
Change-Id: I71e100c549b4ef30699efe6363b72eb792ad1c23
PiperOrigin-RevId: 158243584
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new docs/ directory in the bazel source tree will only contain the Bazel
docs site, which is hosted at docs.bazel.build. This change deletes the
marketing site and blog, which have been migrated to the bazel-website and
bazel-blog GitHub repositories respectively.
This change also updates the serve-docs.sh and ci/build.sh under scripts/ in
preparation for publishing the docs site.
Note that to help make reviews more manageable, this change is limited to
moving files to their new locations. Here are the follow-up changes:
* Update all links in docs to remove versions/master in paths and to add
correct bazel.build subdomain when linking to pages on the marketing site
or the blog.
* Set up versioned directories on GCS bucket and add tooling for versioning
docs
This change is also coordinated with
https://bazel-review.googlesource.com/c/11568/ to have the PublishSite job
publish to docs.bazel.build rather than www.bazel.build.
Issue #2397
RELNOTES: None
PiperOrigin-RevId: 157612651
|