| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
This is a prerequisite for the next javac update, and mirrors the
approach used for other javac-based tests in Bazel (e.g.
BazelJavaCompilerTest).
PiperOrigin-RevId: 152779250
|
|
|
|
| |
PiperOrigin-RevId: 151461345
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Fixed all errors.
*** Original change description ***
Automated [] rollback of commit 69a127b8f4e353ecb163688ed3271fb47e0f385d.
--
PiperOrigin-RevId: 149092038
MOS_MIGRATED_REVID=149092038
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
[] has detected that 500 or more targets failed to build at commit 69a127b8f4e353ecb163688ed3271fb47e0f385d, each of which successfully built at the prior CL that affected them.
[] double-checked that //javatests/com/google/apphosting/tests/usercode:Security_StubTest
built at 148995024. The verification run was:
[]
but the same target failed to build at 148995025. The [] link for this run is available here: []
To see all targets that ran, along with their final status, visit: []
Questions? Comments? See the URL.
go/autorollback
*** Original change description ***
ijar: use bazel's file utilities
This change not only implements ijar for Windows
(with MSVC), but also fixes a bug in
mapped_file_windows (path conversion didn't make
the input path absolute, so we could not build
java code with the MSYS-less bazel).
Fixes https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148998092
MOS_MIGRATED_REVID=148998092
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change not only implements ijar for Windows
(with MSVC), but also fixes a bug in
mapped_file_windows (path conversion didn't make
the input path absolute, so we could not build
java code with the MSYS-less bazel).
Fixes https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148995025
MOS_MIGRATED_REVID=148995025
|
|
|
|
|
|
|
|
| |
--
Change-Id: I6ce9c6afe14dfaff8a60ae90ee1504684d9cc61c
Reviewed-on: https://cr.bazel.build/9117
PiperOrigin-RevId: 148891361
MOS_MIGRATED_REVID=148891361
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148887981
MOS_MIGRATED_REVID=148887981
|
|
|
|
|
| |
PiperOrigin-RevId: 148768294
MOS_MIGRATED_REVID=148768294
|
|
|
|
|
|
|
|
|
|
|
| |
We may not assume that those are pulled in by other
header files; in fact, they are not on FreeBSD stable/11.
--
Change-Id: Ic976cc71968aab0a1c3d6652fe8d8f1c4afa480b
Reviewed-on: https://cr.bazel.build/8145
PiperOrigin-RevId: 143970238
MOS_MIGRATED_REVID=143970238
|
|
|
|
|
|
| |
Commit 6d31cb was an internal reorganization of google repository
that should have resulted in no change. Due to a bug in our export
process it deleted several files in third_party.
|
|
|
|
|
| |
PiperOrigin-RevId: 142666783
MOS_MIGRATED_REVID=142666783
|
|
|
|
|
|
|
|
| |
0 is not a valid DOS timestamp, days and months start at 1.
--
PiperOrigin-RevId: 141818782
MOS_MIGRATED_REVID=141818782
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 645dbc4 moved the file stating logic to
platform_utils.cc into the `stat_file` method,
then commit 8d6da00 added error reporting to that
method so callers wouldn't need to report errors
on their own. Problem is, one of the callers was
using stat_file for simple file existence checking
so reporting an error there was spurious.
Fixes https://github.com/bazelbuild/bazel/issues/2201
--
Change-Id: I40d1ee2bad8f3d03627c0b5c0bfd593bb5289d23
Reviewed-on: https://cr.bazel.build/7810
PiperOrigin-RevId: 141739581
MOS_MIGRATED_REVID=141739581
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can now build //third_party/ijar/...:all with
--cpu=x64_windows_msvc.
We also have to use --output_user_root=/c/tmp
or something similarly short because
//third_party/zlib tickles https://github.com/bazelbuild/bazel/issues/2145
This change takes us closer to compiling Bazel
with MSVC.
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 140846600
MOS_MIGRATED_REVID=140846600
|
|
|
|
|
|
|
|
|
|
|
|
| |
zip_main.cc no longer needs <unistd.h>.
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140724421
|
|
|
|
|
|
|
|
|
|
|
|
| |
zip_main.cc no longer needs <unistd.h>.
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140723658
|
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140722341
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
Also update the StatFile method added by
unknown commit to report any errors.
See https://github.com/bazelbuild/bazel/issues/2157
See https://github.com/bazelbuild/bazel/issues/2107
--
MOS_MIGRATED_REVID=140719249
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2107 and https://github.com/bazelbuild/bazel/issues/2157
--
MOS_MIGRATED_REVID=140717828
|
|
|
|
|
|
|
|
|
|
|
| |
The behavior of ftruncate on WSL is not same as standard Linux due to a bug, it'll fail on maped file.
This commit fix the bug by munmap the file before ftruncate.
Closes #2108.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2108
MOS_MIGRATED_REVID=140134115
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135345337
|
|
|
|
|
|
|
| |
Those tests requires JDK8 features, just ignore them.
--
MOS_MIGRATED_REVID=135264862
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Other projects may depend on Ijar without wanting to depend on Bazel.
*** Original change description ***
Ijar: use utilities from Bazel's source
Remove a duplicate implementation of JoinPath.
--
MOS_MIGRATED_REVID=135088616
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Other projects may depend on Ijar without wanting to depend on Bazel.
*** Original change description ***
Ijar: use more utilities from Bazel's source
Remove duplicate implementations from zip_main.cc
--
MOS_MIGRATED_REVID=135086722
|
|
|
|
|
|
|
| |
Remove duplicate implementations from zip_main.cc
--
MOS_MIGRATED_REVID=134797116
|
|
|
|
|
|
|
| |
Remove a duplicate implementation of JoinPath.
--
MOS_MIGRATED_REVID=134778185
|
|
|
|
|
|
|
|
| |
Particulary third_party/ijar:{zip,zlib_client} now
compile with --cpu=x64_windows_msvc.
--
MOS_MIGRATED_REVID=134771232
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update `select` statements in BUILD files with the
new config_setting.
This is a first step on a long path that leads to
us being able to compile bazel on Windows with
--cpu=x64_windows_msvc. Needless to say, we're not
there yet.
Tested: on Linux, Darwin, Windows/MSYS
--
MOS_MIGRATED_REVID=134534613
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/1826
--
MOS_MIGRATED_REVID=134261731
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134040102
|
|
|
|
|
|
|
| |
class. And add a dummy zlib client.
--
MOS_MIGRATED_REVID=133879880
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129429378
|
|
|
|
|
|
|
|
|
|
|
| |
Examples for how to use <zip_path>=<file> syntax:
zipper c x.zip a/b/__init__.py= # Add an empty file at a/b/__init__.py
zipper c x.zip a/b/main.py=foo/bar/bin.py # Add file foo/bar/bin.py at a/b/main.py
--
Change-Id: I3c09dfb31d082f3ca8036e87affc8d99f7e75fe0
Reviewed-on: https://bazel-review.googlesource.com/#/c/4243
MOS_MIGRATED_REVID=129325719
|
|
|
|
|
|
|
|
| |
This situation arises when a zip file does not contain entries for the
directories themselves, but only the files themselves.
--
MOS_MIGRATED_REVID=129072925
|
|
|
|
|
|
|
| |
$TEST_TMPDIR is not deleted automatically and this can result in the accumulation of a bunch of large files on the CI machines of Bazel because this tests writes 2GB files for testing.
--
MOS_MIGRATED_REVID=128037053
|
|
|
|
|
|
|
| |
Another part of rolling forward #1262.
--
MOS_MIGRATED_REVID=125481356
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125160288
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
repositories
One interesting side effect of how this is implemented is that for external
repositories, bin/ and genfiles/ are combined. External repo output is under
bazel-out/local-fastbuild/repo_name for each repo.
Fixes #1262.
RELNOTES[INC]: Previously, an external repository would be symlinked into the
execution root at execroot/local_repo/external/remote_repo. This changes it to
be at execroot/remote_repo. This may break genrules/Skylark actions that
hardcode execution root paths. If this causes breakages for you, ensure that
genrules are using $(location :target) to access files and Skylark rules are
using http://bazel.io/docs/skylark/lib/File.html's path, dirname, etc.
functions.
--
MOS_MIGRATED_REVID=125095799
|
|
|
|
|
|
|
|
|
|
| |
1. Add ability to specify relative output directory through -d option.
2. Add ability to specify a list of archive entries to extract from the zip file.
Fixes #630.
--
MOS_MIGRATED_REVID=122159723
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=121475668
|
|
|
|
|
|
|
|
| |
This was reported in
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1197
MOS_MIGRATED_REVID=121257152
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES: Bazel's workspace name is now io_bazel. If you are using Bazel's
source as an external repository, then you may want to update the name you're
referring to it as or you'll begin seeing warnings about name mismatches in your
code.
--
MOS_MIGRATED_REVID=120926179
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 790d2f6009d47fe92cf0cd92a1473bbf0141f32e.
*** Reason for rollback ***
Broke non-Bazel projects on ci.bazel.io
Fixes #1168
*** Original change description ***
Move the runfiles for external repositories to under the x.runfiles/ directory
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles....
***
--
MOS_MIGRATED_REVID=120535721
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles.
---
Furthermore, if a Bazel project does not provide a workspace name in the WORKSPACE file, Bazel will now default to using __main__ as the workspace name (instead of "", as previously). The repository's runfiles will appear under x.runfiles/__main__/.
--
MOS_MIGRATED_REVID=120224534
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119581073
|
|
|
|
|
|
|
| |
--
Change-Id: Ia176408e9b59caa85da7eb63fd3d9251a1d3fb40
Reviewed-on: https://bazel-review.googlesource.com/#/c/3328/
MOS_MIGRATED_REVID=119522458
|
|
|
|
|
|
|
| |
This was the last dependency of Bazel that is pulled in from the host system, so now (at least as dependencies go) the source tree of Bazel is now self-contained.
--
MOS_MIGRATED_REVID=119243670
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119053259
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Check the return value of getcwd() and if it fails print
a message to the user and return -1.
This should fix the following warning:
third_party/ijar/zip_main.cc:175:32: warning: ignoring return value of
'char* getcwd(char*, size_t)', declared with attribute
warn_unused_result [-Wunused-result]
getcwd(output_root, PATH_MAX);
--
Change-Id: I8857e484f5baf60289d7c19a128f5a4616ae50e4
Reviewed-on: https://bazel-review.googlesource.com/#/c/3230/
MOS_MIGRATED_REVID=119029402
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118761993
|