New target: `run_unit_tests`. `run_tests` behaves like before. `run_unit_test` skips the SSL tests but runs all else. Before: - run_tests after clean: 479.89s user 216.00s system 465% cpu 2:29.55 total - run_tests only: 263.80s user 155.95s system 416% cpu 1:40.75 total After: - run_tests after clean: 475.84s user 212.90s system 481% cpu 2:23.13 total - run_tests only: 262.45s user 147.73s system 392% cpu 1:44.60 total - run_unit_tests after clean: 384.36s user 65.90s system 578% cpu 1:17.87 total - run_unit_tests only: 172.90s user 5.95s system 556% cpu 32.151 total Marginal improvements even for run_tests because now the SSL test-exclusive parts are compiled in parallel with running the pregenerate check. For comparison, `bazel test --nocache_test_results :crypto_test :ssl_test :decrepit_test :pki_test`: - tests after clean: 1:35.73 total (slower than `run_unit_tests`) - tests only: 31.040 total (comparable to `run_unit_tests`, but lacks pregenerate and Go tests) Change-Id: I8764f318f8373b5d108b4e1cced4627c6a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/99407 Reviewed-by: Xiangfei Ding <xfding@google.com> Commit-Queue: Rudolf Polzer <rpolzer@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
Project links:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: