feedback-to-code/mozzarella huggingface dataset:
Repository: bazelbuild/bazel
Issue: [6.0.0] Missing linkopts when building a cc_test

Forked from #16877

Issue comments:
@kshyanashree Please cherry pick https://github.com/bazelbuild/bazel/commit/cd40666001e8d599bb61735898c195c6d2fae55b to close this one, thanks! 
After cherry pick this one, we can create rc3 ;)
> @kshyanashree Please cherry pick [cd40666](https://github.com/bazelbuild/bazel/commit/cd40666001e8d599bb61735898c195c6d2fae55b) to close this one, thanks!

Hi @meteorcloudy ! I have already cherry-picked this one here , but  check is failing due to missing CLA #16886 . Wanted to check with you. Thanks!
For some reason the original commit was showing up as being authored by "noreply@google.com", which can't pass the CLA check. I think we can just force merge that PR.
Merged in #16886

Let's create an rc3!
Sure, Thanks @Wyverald!

Pull request review comments:

Patch that resolved the issue:
diff --git a/src/main/starlark/builtins_bzl/common/cc/cc_binary.bzl b/src/main/starlark/builtins_bzl/common/cc/cc_binary.bzl
index 48a4f684d641fd..23982806a59d4d 100644
--- a/src/main/starlark/builtins_bzl/common/cc/cc_binary.bzl
+++ b/src/main/starlark/builtins_bzl/common/cc/cc_binary.bzl
@@ -366,12 +366,6 @@ def _get_preloaded_deps_from_dynamic_deps(ctx):
 
     return cc_common.merge_cc_infos(direct_cc_infos = cc_infos, cc_infos = cc_infos).linking_context.linker_inputs.to_list()
 
-def _get_canonical_form(label):
-    repository = label.workspace_name
-    if repository == "@":
-        repository = ""
-    return repository + "//" + label.package + ":" + label.name
-
 def _filter_libraries_that_are_linked_dynamically(ctx, cc_linking_context, cpp_config):
     merged_cc_shared_library_infos = merge_cc_shared_library_infos(ctx)
     preloaded_deps = _get_preloaded_deps_from_dynamic_deps(ctx)
@@ -399,7 +393,7 @@ def _filter_libraries_that_are_linked_dynamically(ctx, cc_linking_context, cpp_c
             continue
         linker_inputs_seen[stringified_linker_input] = True
         owner = str(linker_input.owner)
-        if owner not in link_dynamically_labels and (owner in link_statically_labels or _get_canonical_form(ctx.label) == owner):
+        if owner not in link_dynamically_labels and (owner in link_statically_labels or str(ctx.label) == owner):
             if owner in link_once_static_libs_map:
                 linked_statically_but_not_exported.setdefault(link_once_static_libs_map[owner], []).append(owner)
             else:


Test patch:
Repository: bazelbuild/bazel
Issue: `cc_test` rules trigger remote JDK download (~200 MB)
Labels: type: bug
P2
team-Rules-CPP

### Description of the problem / feature request:

`cc_test` rules trigger remote JDK download (~200 MB), which is undesirable when operating under constraints on storage capacity and/or network capacity. https://en.wikipedia.org/wiki/Principle_of_least_astonishment also applies.

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

```
$ rm -rf $HOME/.cache/bazel
$ git clone https://github.com/google/re2.git
$ cd re2
$ bazel build //:all --experimental_repository_resolved_file=resolved.bzl
$ grep openjdk resolved.bzl
$ bazel query 'somepath(//:all, @remote_coverage_tools//:all)'
```

### What operating system are you running Bazel on?

Linux

### What's the output of `bazel info release`?

```
release 5.0.0
```


Issue comments:
cc @comius @c-mita 
It's seems the issue is that cc_tests unconditionally pulls those coverage tools dependencies.
https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/analysis/test/TestConfiguration.java;l=255-270

Pull request review comments:

Patch that resolved the issue:
diff --git a/src/main/java/com/google/devtools/build/lib/analysis/BUILD b/src/main/java/com/google/devtools/build/lib/analysis/BUILD
index 350541aee2ad63..8076305da098c7 100644
--- a/src/main/java/com/google/devtools/build/lib/analysis/BUILD
+++ b/src/main/java/com/google/devtools/build/lib/analysis/BUILD
@@ -2541,7 +2541,7 @@ java_library(
         "//src/main/java/com/google/devtools/build/lib/concurrent",
         "//src/main/java/com/google/devtools/build/lib/starlarkbuildapi/test",
         "//src/main/java/com/google/devtools/common/options",
-        "//third_party:jsr305",
+        "//third_party:jsr305_checked_in",
     ],
 )
 
diff --git a/src/main/java/com/google/devtools/build/lib/rules/BUILD b/src/main/java/com/google/devtools/build/lib/rules/BUILD
index 2a256ca6b2e02a..0b555ff8067976 100644
--- a/src/main/java/com/google/devtools/build/lib/rules/BUILD
+++ b/src/main/java/com/google/devtools/build/lib/rules/BUILD
@@ -59,6 +59,7 @@ java_library(
         "//src/main/java/com/google/devtools/build/lib/actions",
         "//src/main/java/com/google/devtools/build/lib/actions:artifacts",
         "//src/main/java/com/google/devtools/build/lib/analysis:analysis_cluster",
+        "//src/main/java/com/google/devtools/build/lib/analysis:configured_target",
         "//src/main/java/com/google/devtools/build/lib/analysis:test/coverage_configuration",
         "//src/main/java/com/google/devtools/build/lib/analysis:test/test_configuration",
         "//src/main/java/com/google/devtools/build/lib/analysis:test/test_trimming_transition_factory",


Test patch:
Repository: bazelbuild/bazel
Issue: No writable permission for /tmp if /tmp is symbolic link
Labels: type: bug
P3
team-Local-Exec
help wanted

### Description of the bug:


Hi,

In some cases there is no enough space for /tmp to build big project, usually we will set /tmp as a symbolic link to local path (ex, /tmp -> /home/xxx/tmp)

For bazel build we will have no writable permission for /tmp 
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
clang-17: error: unable to make temporary file: Read-only file system

From the sandbox_debug log we can see the canonical path is remounted as read only.
src/main/tools/linux-sandbox-pid1.cc:311: writable: /tmp
src/main/tools/linux-sandbox-pid1.cc:405: remount ro: /home/xxx/tmp

https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxedSpawnRunner.java
430 writableDirs.add(fs.getPath("/tmp"));
So it could be a bug for linux sandbox spaw runner. it can be changed as below
430 writableDirs.add(fs.getPath("/tmp").resolveSymbolicLinks());

Thanks

### Which category does this issue belong to?


Java Rules

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.


set /tmp as a symbolic link and build kernel modules with bazel which need to write files into /tmp directory

### Which operating system are you running Bazel on?


linux

### What is the output of `bazel info release`?


bazel 7.0.0  all pre release

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.


bazel 7.0.0  all preversion dist

### What's the output of `git remote get-url origin; git rev-parse master; git rev-parse HEAD` ?


_No response_

### Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.


no

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Issue comments:
how can i submit the changes?
> how can i submit the changes?

If it's really just this line, you could use GitHub's web interface to edit the file and create a Pull Request from that.
Feel free to send a PR, we are happy to review it!

Pull request review comments:

Patch that resolved the issue:
diff --git a/src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxedSpawnRunner.java b/src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxedSpawnRunner.java
index 3b2582f8647abc..29d342e14b08b6 100644
--- a/src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxedSpawnRunner.java
+++ b/src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxedSpawnRunner.java
@@ -427,7 +427,7 @@ protected ImmutableSet<Path> getWritableDirs(
     }
     FileSystem fs = sandboxExecRoot.getFileSystem();
     writableDirs.add(fs.getPath("/dev/shm").resolveSymbolicLinks());
-    writableDirs.add(fs.getPath("/tmp"));
+    writableDirs.add(fs.getPath("/tmp").resolveSymbolicLinks());
 
     return writableDirs.build();
   }


Test patch:
Repository: bazelbuild/bazel
Issue: typos in readme

A emphasis on automated testing -> An emphasis on automated testing

"Find more background about Bazel in our FAQ" -- needs a period after FAQ.

"The test environment is described the test encyclopedia." -- described _in_ the test encyclopedia?


Issue comments:
Thanks, should all be fixed.


Pull request review comments:

Patch that resolved the issue:
diff --git a/README.md b/README.md
index a84d7b1b67a686..4bec7211edf027 100644
--- a/README.md
+++ b/README.md
@@ -25,17 +25,17 @@ Find more background about Bazel in our [FAQ](docs/FAQ.md)
 
 ## Getting Started
 
-  * How to [install Bazel](//bazel.io/docs/install.html)
-  * How to [get started using Bazel](//bazel.io/docs/getting-started.html)
-  * The Bazel command line is documented in the  [user manual](//bazel.io/docs/bazel-user-manual.html)
-  * The rule reference documentation is in the [build encyclopedia](//bazel.io/docs/build-encyclopedia.html)
-  * How to [use the query command](//bazel.io/docs/query.html)
-  * How to [extend Bazel](//bazel.io/docs/skylark/index.html)
-  * The test environment is described in the [test encyclopedia](//bazel.io/docs/test-encyclopedia.html)
+  * How to [install Bazel](http://bazel.io/docs/install.html)
+  * How to [get started using Bazel](http://bazel.io/docs/getting-started.html)
+  * The Bazel command line is documented in the  [user manual](http://bazel.io/docs/bazel-user-manual.html)
+  * The rule reference documentation is in the [build encyclopedia](http://bazel.io/docs/build-encyclopedia.html)
+  * How to [use the query command](http://bazel.io/docs/query.html)
+  * How to [extend Bazel](http://bazel.io/docs/skylark/index.html)
+  * The test environment is described in the [test encyclopedia](http://bazel.io/docs/test-encyclopedia.html)
 
 * About the Bazel project:
 
-  * How to [contribute to Bazel](//bazel.io/docs/contributing.html)
-  * Our [governance plan](//bazel.io/docs/governance.html)
-  * Future plans are in the [roadmap](//bazel.io/docs/roadmap.html)
-  * For each feature, which level of [support](//bazel.io/docs/support.html) to expect.
+  * How to [contribute to Bazel](http://bazel.io/docs/contributing.html)
+  * Our [governance plan](http://bazel.io/docs/governance.html)
+  * Future plans are in the [roadmap](http://bazel.io/docs/roadmap.html)
+  * For each feature, which level of [support](http://bazel.io/docs/support.html) to expect.


Test patch:
Repository: bazelbuild/bazel
Issue: ./compile.sh fails with macports

Following the instructions at http://bazel.io/docs/install.html for a Mac using macports, I get:

<pre>
$ ./compile.sh 
cp: /include/archive.h: No such file or directory
cp: /include/archive_entry.h: No such file or directory
</pre>


This seems to fix the problem:

<pre>
$ git diff ./compile.sh 
diff --git a/compile.sh b/compile.sh
index c4ff9bf..3a9231a 100755
--- a/compile.sh
+++ b/compile.sh
@@ -99,7 +99,8 @@ EOF
 
       elif [[ -e $macports_header ]]; then
         # For use with Macports.
-        archive_dir=$(dirname $(dirname $macports_header)) rm -f fromhost/*.[ah]
+        archive_dir=$(dirname $(dirname $macports_header))
+        rm -f fromhost/*.[ah]
         touch fromhost/empty.c
         cp "${archive_dir}"/include/{archive.h,archive_entry.h} fromhost/
         cp "${archive_dir}"/lib/{libarchive,liblzo2,liblzma,libcharset,libbz2,libxml2,libz,libiconv}.a \
</pre>


Issue comments:
Nice catch. Can you submit your patch with a github pull request?

OK, I sent a pull request.  I haven't done that before, so let me know if anything is fishy.

https://github.com/google/bazel/commit/e93638335955ff8d7e948f2d385319e458ee0ca4


Pull request review comments:

Patch that resolved the issue:
diff --git a/compile.sh b/compile.sh
index c4ff9bf3944aa0..3a9231ac06b55e 100755
--- a/compile.sh
+++ b/compile.sh
@@ -99,7 +99,8 @@ EOF
 
       elif [[ -e $macports_header ]]; then
         # For use with Macports.
-        archive_dir=$(dirname $(dirname $macports_header)) rm -f fromhost/*.[ah]
+        archive_dir=$(dirname $(dirname $macports_header))
+        rm -f fromhost/*.[ah]
         touch fromhost/empty.c
         cp "${archive_dir}"/include/{archive.h,archive_entry.h} fromhost/
         cp "${archive_dir}"/lib/{libarchive,liblzo2,liblzma,libcharset,libbz2,libxml2,libz,libiconv}.a \


Test patch:
Repository: bazelbuild/bazel
Issue: Missing docs pages / broken links
Labels: type: documentation (cleanup)

I was reading through the Docs on http://bazel.io/docs/install.html and there are some broken links on the Skylark Rules section of the side menu.

These links return 404:
- Java AppEngine - http://bazel.io/docs/be/appengine.html
- C# - http://bazel.io/docs/be/dotnet.html
- D - http://bazel.io/docs/be/d.html
- Groovy - http://bazel.io/docs/be/groovy.html
- Go - http://bazel.io/docs/be/go.html
- Sass - http://bazel.io/docs/be/sass.html

This link returns a page with a redirect link, and that link returns 404:
- Scala - http://bazel.io/docs/be/scala.html

Apologies if this is the wrong repo to report this, but I couldn't find a better one in the bazelbuild org.


Issue comments:
Thanks for the report!  We recently moved all of these rules to their own repos (e.g., https://github.com/bazelbuild/rule_appengine), and I think we're still updating how their documentation is generated.


Pull request review comments:

Patch that resolved the issue:
diff --git a/src/main/java/com/google/devtools/build/docgen/templates/be/be-nav.vm b/src/main/java/com/google/devtools/build/docgen/templates/be/be-nav.vm
index 0aa490835df6be..671b5a691deefe 100644
--- a/src/main/java/com/google/devtools/build/docgen/templates/be/be-nav.vm
+++ b/src/main/java/com/google/devtools/build/docgen/templates/be/be-nav.vm
@@ -34,7 +34,7 @@
   <li><a href="${bazelbuildGithub}/rules_go" target="_blank">Go</a></li>
   <li><a href="${bazelbuildGithub}/rules_jsonnet" target="_blank">Jsonnet</a></li>
   <li><a href="${path}/pkg.html">Packaging</a></li>
-  <li><a href="${bazelbuildGithub}/rules_rust target="_blank"">Rust</a></li>
+  <li><a href="${bazelbuildGithub}/rules_rust" target="_blank"">Rust</a></li>
   <li><a href="${bazelbuildGithub}/rules_sass" target="_blank">Sass</a></li>
   <li><a href="${bazelbuildGithub}/rules_scala" target="_blank">Scala</a></li>
 </ul>


Test patch:
Repository: bazelbuild/bazel
Issue: Documentation- java_test use_testrunner mistake
Labels: type: documentation (cleanup)
P3

Hi,
I think the documentation of the java_test use_testrunner property is mistaken.
It talks about `com.google.testing.junit.runner.GoogleTestRunner` while I think that was superseded by `BazelTestRunner` which is also mentioned which adds to the confusion.
I think the first mention should also change to `BazelTestRunner`.
Hope I'm not talking gibberish.


Issue comments:
The default value of `use_testrunner` is 1 and default behavior is to use `BazelTestRunner`, if a user needs to use this property, he would set `use_testrunner = 0` to use `GoogleTestRunner`.

Maybe we should make it more clear. ;)

Sorry, what I said above was totally wrong. The GoogleTestRunner doesn't exist in Bazel code. Setting `use_testrunner = 0` will just run the test java binary without any test runner. We should definitely update the document!

PR?
On יום ג׳, 7 ביוני 2016 at 17:01 Yun Peng notifications@github.com wrote:

> Sorry, what I said above was totally wrong. The GoogleTestRunner doesn't
> exist in Bazel code. Setting use_testrunner = 0 will just run the test
> java binary without any test runner. We should definitely update the
> document!
> 
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> https://github.com/bazelbuild/bazel/issues/1345#issuecomment-224289479,
> or mute the thread
> https://github.com/notifications/unsubscribe/ABUIF5huEY8z07V-SIbEoCjaBjXtbjjqks5qJXm2gaJpZM4Iv4Fh
> .

Yeah, that would be nice. :)


Pull request review comments:

Patch that resolved the issue:
diff --git a/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java b/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java
index cf195562209cf9..fc40911439b36f 100644
--- a/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java
+++ b/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java
@@ -290,7 +290,7 @@ generated by the wrapper script includes the name of the main class followed by
           .add(attr("jvm_flags", STRING_LIST))
           /* <!-- #BLAZE_RULE($base_java_binary).ATTRIBUTE(use_testrunner) -->
           Use the
-          <code>com.google.testing.junit.runner.GoogleTestRunner</code> class as the
+          <code>com.google.testing.junit.runner.BazelTestRunner</code> class as the
           main entry point for a Java program.
 
           You can use this to override the default


Test patch:
Repository: bazelbuild/bazel
Issue: http://bazel.io should redirect to https://bazel.io
Labels: type: documentation (cleanup)
P2

https://bazel.io is now live, but http://bazel.io does not redirect to the https site.


Issue comments:

Pull request review comments:
replace to www.bazel.io?


Patch that resolved the issue:
diff --git a/.gitignore b/.gitignore
index e6d98586835c48..d5396a246de715 100644
--- a/.gitignore
+++ b/.gitignore
@@ -13,3 +13,5 @@
 /bazel-testlogs
 /bazel.iml
 /output/
+/.sass-cache/
+/production/
diff --git a/site/_includes/head.html b/site/_includes/head.html
index 57bad5c9ee0246..7bd812a48032ec 100644
--- a/site/_includes/head.html
+++ b/site/_includes/head.html
@@ -8,7 +8,11 @@
       var current_url = window.location.href;
       var bad_url = new RegExp("^https?://bazelbuild.github.io/bazel/");
       if (bad_url.test(current_url)) {
-        window.location.replace(current_url.replace(bad_url, "http://bazel.io/"));
+        window.location.replace(current_url.replace(bad_url, "https://www.bazel.io/"));
+      }
+      var http_url = new RegExp("^http://(www\.)?bazel.io/");
+      if (http_url.test(current_url)) {
+        window.location.replace(current_url.replace(http_url, "https://www.bazel.io/"));
       }
     </script>
 


Test patch:
Repository: bazelbuild/bazel
Issue: Windows, chocolatey: support drive letters other than C: in chocolatey package.
Labels: P3
platform: windows

At least in `chocolateyinstall.ps1`, line 53, and maybe other places

Issue comments:
@petemounce @laszlocsomor 

Woah woah woah, regex find and replace in powershell? What have I let myself in for. Are different drives really necessary? :p

Yeah, sure. I'll get that done.

Help us Obi-Wan, you're the only PS expert! :)

Done.


Pull request review comments:
I think you don't need to match $2 if you're outputting it unaltered.

That's true. I like this pattern more since it's more explicit, but I don't feel strongly.

ok


Patch that resolved the issue:
diff --git a/scripts/packages/chocolatey/tools/chocolateyinstall.ps1 b/scripts/packages/chocolatey/tools/chocolateyinstall.ps1
index 9afd433d8ef29e..fbd3cc32b0c653 100644
--- a/scripts/packages/chocolatey/tools/chocolateyinstall.ps1
+++ b/scripts/packages/chocolatey/tools/chocolateyinstall.ps1
@@ -2,13 +2,14 @@ $ErrorActionPreference = 'Stop'; # stop on all errors
 $packageName = 'bazel'
 
 $toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
-$p = ((gc "$toolsDir\params.json") -join "`n") | convertfrom-json
+$json = gc "$toolsDir\params.json"
+$p = (($json) -join "`n") | convertfrom-json
 
 $packageDir = Split-Path -parent $toolsDir
 $binRoot = (Get-ToolsLocation) -replace "\\", "/"
 
 write-host "Read params from json"
-write-host $p
+write-host (convertto-json $p)
 
 Install-ChocolateyZipPackage -PackageName "$packageName" `
   -Url "$($p.package.uri)" `
@@ -50,7 +51,7 @@ if ($packageParameters)
 }
 Install-ChocolateyPath -PathToInstall "$msys2Path\usr\bin" -PathType "Machine"
 
-$addToMsysPath = ($packageDir -replace 'c:\\','/c/') -replace '\\','/'
+$addToMsysPath = ($packageDir -replace '^([a-zA-Z]):\\(.*)','/$1/$2') -replace '\\','/'
 write-host @"
 bazel installed to $packageDir
 


Test patch:
Repository: bazelbuild/bazel
Issue: Homebrew install steps are missing Java install
Labels: type: documentation (cleanup)
P2

I followed https://bazel.build/versions/master/docs/install.html#mac-os-x

and when I type `brew install bazel` I am told that Java 1.8+ is required.

Following Java install steps at https://bazel.build/versions/master/docs/install.html#1-install-jdk-8-2 works

Issue comments:

Pull request review comments:
s/install/installed/

Also, `bazel version` instead of `$ bazel` (don't include the $ for inline snippets).
s/install/installed/

Also, `bazel version` instead of `$ bazel` (don't include the $ for inline snippets).
This seems like useful info to have.
fixed
fixed

fixed

Patch that resolved the issue:
diff --git a/site/versions/master/docs/install.md b/site/versions/master/docs/install.md
index 0a6f9e5b0cbfaf..a7faca3cc6c56a 100644
--- a/site/versions/master/docs/install.md
+++ b/site/versions/master/docs/install.md
@@ -136,25 +136,31 @@ You can also add this command to your `~/.bashrc` file.
 
 Install Bazel on Mac OS X using one of the following methods:
 
-  * [Using Homebrew](#install-on-mac-os-x-homebrew)
-  * [Using binary installer](#install-with-installer-mac-os-x)
+  * [Install using Homebrew](#install-on-mac-os-x-homebrew)
+  * [Install with installer](#install-with-installer-mac-os-x)
   * [Compiling Bazel from source](#compiling-from-source)
 
 
-### <a name="install-on-mac-os-x-homebrew"></a>Using Homebrew
+### <a name="install-on-mac-os-x-homebrew"></a>Install using Homebrew
 
-#### 1. Install Homebrew on Mac OS X (one time setup)
+#### 1. Install JDK 8
+
+JDK 8 can be downloaded from
+[Oracle's JDK Page](http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html).
+Look for "Mac OS X x64" under "Java SE Development Kit". This will download a
+DMG image with an install wizard.
+
+#### 2. Install Homebrew on Mac OS X (one time setup)
 
 `$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"`
 
-#### 2. Install Bazel Homebrew Package
+#### 3. Install Bazel Homebrew Package
 
 `$ brew install bazel`
 
-Once installed, you can upgrade to newer version of Bazel with:
-
-`$ brew upgrade bazel`
+You are all set. You can confirm Bazel is installed successfully by running `bazel version`.
 
+You can later upgrade to newer version of Bazel with `brew upgrade bazel`.
 
 ### <a name="install-with-installer-mac-os-x"></a>Install with installer
 
@@ -216,6 +222,7 @@ $ export PATH="$PATH:$HOME/bin"
 
 You can also add this command to your `~/.bashrc` file.
 
+You are all set. You can confirm Bazel is installed successfully by running `bazel version`.
 
 ## <a name="windows"></a>Windows
 


Test patch: