diff options
| author | Nicolas Lacasse <nlacasse@google.com> | 2019-08-13 11:20:43 -0700 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2019-08-13 11:21:55 -0700 |
| commit | fa3d0e6f63d6ecc9a6566ec80e4a8c7519c6cf76 (patch) | |
| tree | 20d52584852bec4e2fc8b52c79260195cded0c0f /pkg/sentry/vfs/resolving_path.go | |
| parent | 9769a8eaa4b384d1b7db9f06edf28a6331cd2b64 (diff) | |
Bump Bazel to v0.28.0
The new version has a change in behavior when using a custom platform:
* Old behavior: rules that don't require a toolchain used host_platform, no
matter what execution platforms are specified.
* New behavior: rules that don't require a toolchain use standard platform
resolution that starts with execution platforms.
As part of this change, we cannot use the "extra_exectution_platforms" flag
provided by the default bazelrc. I got rid of the default bazelrc file, and
made our custom .bazelrc as minimal as possible.
PiperOrigin-RevId: 263176802
Diffstat (limited to 'pkg/sentry/vfs/resolving_path.go')
0 files changed, 0 insertions, 0 deletions