Home
last modified time | relevance | path

Searched +full:build +full:- +full:and +full:- +full:test (Results 1 – 25 of 1329) sorted by relevance

12345678910>>...54

/external/mbedtls/tests/scripts/
Dall.sh6 # SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
15 # -------
20 # ---------------
22 # Warning: the test is destructive. It includes various build modes and
23 # configurations, and can and will arbitrarily change the current CMake
28 # After running this script, the CMake cache will be lost and CMake
32 # * Basic Unix tools (Windows users note: a Unix-style find must be before
37 # * GCC and Clang (recent enough for using ASan with gcc and MemSan with clang, or valgrind)
39 # * arm-gcc and mingw-gcc
40 # * ArmCC 5 and ArmCC 6, unless invoked with --no-armcc
[all …]
/external/openthread/third_party/mbedtls/repo/tests/scripts/
Dall.sh6 # SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
15 # -------
20 # ---------------
22 # Warning: the test is destructive. It includes various build modes and
23 # configurations, and can and will arbitrarily change the current CMake
28 # After running this script, the CMake cache will be lost and CMake
32 # * Basic Unix tools (Windows users note: a Unix-style find must be before
37 # * GCC and Clang (recent enough for using ASan with gcc and MemSan with clang, or valgrind)
39 # * arm-gcc and mingw-gcc
40 # * ArmCC 5 and ArmCC 6, unless invoked with --no-armcc
[all …]
/external/grpc-grpc/tools/buildgen/
Dextract_metadata_from_bazel_xml.py8 # http://www.apache.org/licenses/LICENSE-2.0
13 # See the License for the specific language governing permissions and
16 # Script to extract build metadata from bazel BUILD.
17 # To avoid having two sources of truth for the build metadata (build
19 # of bazel BUILD files and generates a YAML file (currently called
20 # build_autogenerated.yaml). The format and semantics of the generated YAML files
21 # is chosen to match the format of a "build.yaml" file, which used
22 # to be build the source of truth for gRPC build before bazel became
23 # the primary build system.
24 # A good basic overview of the "build.yaml" format is available here:
[all …]
/external/rust/crates/grpcio-sys/grpc/tools/buildgen/
Dextract_metadata_from_bazel_xml.py8 # http://www.apache.org/licenses/LICENSE-2.0
13 # See the License for the specific language governing permissions and
16 # Script to extract build metadata from bazel BUILD.
17 # To avoid having two sources of truth for the build metadata (build
19 # of bazel BUILD files and generates a YAML file (currently called
20 # build_autogenerated.yaml). The format and semantics of the generated YAML files
21 # is chosen to match the format of a "build.yaml" file, which used
22 # to be build the source of truth for gRPC build before bazel became
23 # the primary build system.
24 # A good basic overview of the "build.yaml" format is available here:
[all …]
/external/apache-xml/test/java/xdocs/sources/tests/
Dgetstarted.xml3 <!--
12 * http://www.apache.org/licenses/LICENSE-2.0
17 * See the License for the specific language governing permissions and
19 -->
24 <li><link anchor="how-to-build">Building the Tests</link></li>
30 <jump href="http://xml.apache.org/xalan-j/readme.html#build">building Xalan-J</jump> and with
32 <p>Set JAVA_HOME, and have your classes.zip or tools.jar in the CLASSPATH.</p>
33 <p>Here are some sample commands to build and run tests:</p>
35 …<br/><code>checkout xml-xalan/java </code> Get the Xalan-J code (or simply get a nightly build or…
36 <br/><code>cd xml-xalan/java </code>
[all …]
/external/tinyxml2/.github/workflows/
Dtest.yml1 name: Test
4 test:
7 fail-fast: false
9 os: [ windows-2019, macos-latest, ubuntu-20.04 ]
12 - os: windows-2019
17 - os: ubuntu-20.04
20 - os: macos-latest
23 - cmake: 3.15
25 - cmake: 3.x
31 runs-on: ${{ matrix.os }}
[all …]
/external/armnn/
DBuildGuideAndroidNDK.md1 # How to use the Android NDK to build Arm NN
3 - [Introduction](#introduction)
4 - [Initial Setup](#initial-setup)
5 - [Download the Android NDK and make a standalone toolchain](#download-the-android-ndk-and-make-a-s…
6 - [Install Cmake](#install-cmake)
7 - [Build Flatbuffers](#build-flatbuffers)
8 - [Download Arm NN](#download-arm-nn)
9 - [Get And Build TFLite](#get-and-build-tflite)
10 - [Build Arm Compute Library](#build-arm-compute-library)
11 - [Build Arm NN](#build-arm-nn)
[all …]
/external/fsverity-utils/scripts/
Drun-tests.sh2 # SPDX-License-Identifier: MIT
5 # Use of this source code is governed by an MIT-style
10 # Test script for fsverity-utils. Runs 'make check' in lots of configurations,
11 # runs static analysis, and does a few other tests.
13 # Note: for more test coverage, in addition to running this script, also build
14 # fsverity-utils into a kvm-xfstests test appliance and run
15 # 'kvm-xfstests -c ext4,f2fs -g verity'
17 set -e -u -o pipefail
31 TMPDIR=$(mktemp -d -t libfsverity_test.XXXXXXXXX)
32 trap 'rm -r "$TMPDIR"' EXIT
[all …]
/external/sdv/vsomeip/test/
Dreadme.txt1 Configuration Test
2 ------------------
3 To start the configuration test from the build directory do:
5 ./configuration-test -someip ../config/vsomeip-test.json
9 2015-02-10 08:47:31.503874 [info] Test "HOST ADDRESS" succeeded.
10 2015-02-10 08:47:31.507609 [info] Test "HAS CONSOLE" succeeded.
11 2015-02-10 08:47:31.507865 [info] Test "HAS FILE" succeeded.
12 2015-02-10 08:47:31.508001 [info] Test "HAS DLT" succeeded.
13 2015-02-10 08:47:31.508143 [info] Test "LOGFILE" succeeded.
14 2015-02-10 08:47:31.508315 [info] Test "LOGLEVEL" succeeded.
[all …]
/external/cronet/third_party/libc++/src/docs/
DTestingLibcxx.rst13 libc++ uses LIT to configure and run its tests.
15 The primary way to run the libc++ tests is by using ``make check-cxx``.
18 configurations it is important to customize the way LIT builds and runs
20 test libc++.
27 -----
29 After building libc++, you can run parts of the libc++ test suite by simply
30 running ``llvm-lit`` on a specified test or directory. If you're unsure
32 ``cxx-test-depends`` target. For example:
34 .. code-block:: bash
36 $ cd <monorepo-root>
[all …]
/external/fmtlib/test/
DCMakeLists.txt5 set(TEST_MAIN_SRC test-main.cc gtest-extra.cc gtest-extra.h util.cc)
6 add_library(test-main STATIC ${TEST_MAIN_SRC})
7 target_include_directories(test-main PUBLIC
9 target_link_libraries(test-main gtest fmt)
13 # (Wstringop-overflow) - [meta-bug] bogus/missing -Wstringop-overflow warnings
15 # Bogus -Wstringop-overflow warning
17 # [10 Regression] spurious -Wstringop-overflow writing to a trailing array plus offset
19 if (CMAKE_CXX_COMPILER_ID MATCHES "GNU" AND
21 target_compile_options(${name} PRIVATE -Wno-stringop-overflow)
23 target_link_libraries(${name} -Wno-stringop-overflow)
[all …]
/external/libaom/
DREADME.md6 1. [Building the lib and applications](#building-the-library-and-applications)
7 - [Prerequisites](#prerequisites)
8 - [Get the code](#get-the-code)
9 - [Basics](#basic-build)
10 - [Configuration options](#configuration-options)
11 - [Dylib builds](#dylib-builds)
12 - [Debugging](#debugging)
13 - [Cross compiling](#cross-compiling)
14 - [Sanitizer support](#sanitizers)
15 - [MSVC builds](#microsoft-visual-studio-builds)
[all …]
/external/deqp/external/openglcts/
DREADME.md1 OpenGL and OpenGL ES 2.0/3.X Conformance Test Instructions
4 This document describes how to build, port, and run the OpenGL and OpenGL ES
5 2.0/3.X conformance tests, and how to verify and submit test results.
8 Up-to-date documentation for dEQP is available at:
10 * [The VK-GL-CTS wiki for Khronos members](https://gitlab.khronos.org/Tracker/vk-gl-cts/wikis/home)
11 * [The VK-GL-CTS wiki for non-Khronos members](https://github.com/KhronosGroup/VK-GL-CTS/wiki)
15 ------------------------
16 - [OpenGL and OpenGL ES 2.0/3.X Conformance Test Instructions](#opengl-and-opengl-es-203x-conforman…
17 - [Contents](#contents)
18 - [Test History](#test-history)
[all …]
/external/e2fsprogs/.github/workflows/
Dci.yml4 DEF_CFLAGS: -O2 -g -Wall
7 gcc-build-and-test:
8 name: Build and test with gcc
9 runs-on: ubuntu-latest
11 - uses: actions/checkout@v3
12 - run: ./configure CC=gcc CFLAGS="$DEF_CFLAGS"
13 - run: make -j8 check V=1 CFLAGS_WARN="-Werror"
14 - run: make -j8 install V=1 DESTDIR=$PWD/installdir
15 - run: make -j8 uninstall V=1 DESTDIR=$PWD/installdir
17 clang-build-and-test:
[all …]
/external/cronet/third_party/googletest/src/docs/
Dquickstart-bazel.md3 This tutorial aims to get you up and running with GoogleTest using the Bazel
4 build system. If you're using GoogleTest for the first time or need a refresher,
13 * [Bazel](https://bazel.build/), the preferred build system used by the
20 [Bazel installation guide](https://docs.bazel.build/versions/main/install.html).
29 [Bazel workspace](https://docs.bazel.build/versions/main/build-ref.html#workspace)
31 software you want to build. Each workspace directory has a text file named
33 dependencies required to build the outputs.
41 Next, you’ll create the `WORKSPACE` file to specify dependencies. A common and
43 [Bazel external dependency](https://docs.bazel.build/versions/main/external.html)
45 [`http_archive` rule](https://docs.bazel.build/versions/main/repo/http.html#http_archive).
[all …]
/external/cronet/third_party/boringssl/src/third_party/googletest/docs/
Dquickstart-bazel.md3 This tutorial aims to get you up and running with GoogleTest using the Bazel
4 build system. If you're using GoogleTest for the first time or need a refresher,
13 * [Bazel](https://bazel.build/), the preferred build system used by the
20 [Bazel installation guide](https://bazel.build/install).
28 [Bazel workspace](https://docs.bazel.build/versions/main/build-ref.html#workspace)
30 software you want to build. Each workspace directory has a text file named
32 dependencies required to build the outputs.
40 Next, you’ll create the `WORKSPACE` file to specify dependencies. A common and
42 [Bazel external dependency](https://docs.bazel.build/versions/main/external.html)
44 [`http_archive` rule](https://docs.bazel.build/versions/main/repo/http.html#http_archive).
[all …]
/external/googletest/docs/
Dquickstart-bazel.md3 This tutorial aims to get you up and running with GoogleTest using the Bazel
4 build system. If you're using GoogleTest for the first time or need a refresher,
13 * [Bazel](https://bazel.build/), the preferred build system used by the
20 [Bazel installation guide](https://bazel.build/install).
28 [Bazel workspace](https://docs.bazel.build/versions/main/build-ref.html#workspace)
30 software you want to build. Each workspace directory has a text file named
32 dependencies required to build the outputs.
40 Next, you’ll create the `WORKSPACE` file to specify dependencies. A common and
42 [Bazel external dependency](https://docs.bazel.build/versions/main/external.html)
44 [`http_archive` rule](https://docs.bazel.build/versions/main/repo/http.html#http_archive).
[all …]
/external/autotest/server/site_tests/provision_CheetsUpdate/
Dprovision_CheetsUpdate.py2 # Use of this source code is governed by a BSD-style license that can be
15 from autotest_lib.server import test
18 # 2 & 4 are default partitions, and the system boots from one of them.
26 class provision_CheetsUpdate(test.test):
28 Update Android build On the target DUT.
30 This test is designed for ARC++ Treehugger style CQ to update Android image
44 Download the Android test build from the dev server.
46 @param android_build: Android build to test.
47 @param ds: Dev server instance for downloading the test build.
50 logging.info('Generated build name: %s', build_filename)
[all …]
/external/ltp/testcases/open_posix_testsuite/Documentation/
DHOWTO_RunTests4 3. Building and Running the Tests
7 ------------
8 This document describes how to run the tests in the POSIX Test Suite.
10 Our framework currently has the ability to build and run conformance,
11 functional, and stress tests. All tests are built with make all, but
12 certain care should be used when running the stress test suite as the
16 ----------------------------------------------------
19 The build and execution process varies for conformance tests.
21 For definitions tests, the build and execution process is the same since
22 the pass/fail criterion is determine by whether or not the test compiles.
[all …]
/external/icu/icu4c/source/test/intltest/
Dmessageformat2test_fromjson.cpp1 // © 2024 and later: Unicode, Inc. and others.
15 both ICU4C and ICU4J can use, rather than being embedded in code.
18 how much test coverage has been achieved. Most of the testing is
26 https://github.com/unicode-org/message-format-wg/commits/main/spec/message.abnf
28 as of the following commit from 2023-05-09:
29 https://github.com/unicode-org/message-format-wg/commit/194f6efcec5bf396df36a19bd6fa78d1fa2e0867
34 …thub.com/messageformat/messageformat/blob/main/packages/mf2-messageformat/src/__fixtures/test-mess…
42 TestCase test = testBuilder.setPattern("hello") in jsonTests() local
44 .build(); in jsonTests()
45 TestUtils::runTestCase(*this, test, errorCode); in jsonTests()
[all …]
/external/wayland/
D.gitlab-ci.yml1 # This file uses the freedesktop ci-templates to build Wayland and run our
4 # ci-templates uses a multi-stage build process. First, the base container
5 # image is built which contains the core distribution, the toolchain, and
6 # all our build dependencies. This container is aggressively cached; if a
9 # reused for the build. This gives us predictability of build and far
12 # the current date as well as a unique build identifier.
15 # previously used), the build stage executes within this container.
17 # The final stage is used to expose documentation and coverage information,
21 # Apart from the 'variables', 'include', and 'stages' top-level anchors,
27 # variables prefixed with FDO_ and templates prefixed by .fdo are provided
[all …]
/external/openthread/tests/unit/
DREADME.md3 …o build and run OpenThread unit tests. It will be helpful for developers to debug failed unit test…
5 ## Build Simulation
7 …thout building the whole project. So first build OpenThread on the simulation platform, which will…
11 $ script/cmake-build simulation
19 # Make sure you are at the simulation build directory (build/simulation)
20 $ ctest -N
28 # Make sure you are at the simulation build directory (build/simulation)
32 To run a specific unit test, for example, `ot-test-spinel`:
35 # Make sure you are at the simulation build directory (build/simulation)
36 $ ctest -R ot-test-spinel
[all …]
/external/cronet/third_party/google_benchmark/src/
DREADME.md3 …build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://g…
6 …test-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://git…
8 [![Build Status](https://travis-ci.org/google/benchmark.svg?branch=main)](https://travis-ci.org/goo…
32 To get started, see [Requirements](#requirements) and
33 [Installation](#installation). See [Usage](#usage) for a full example and the
36 It may also help to read the [Google Test documentation](https://github.com/google/googletest/blob/…
41 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
50 [Building and installing Python bindings](docs/python_bindings.md)
54 The library can be used with C++03. However, it requires C++11 to build,
55 including compiler and standard library support.
[all …]
/external/google-benchmark/
DREADME.md3 …build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https://g…
6 …test-bindings](https://github.com/google/benchmark/workflows/test-bindings/badge.svg)](https://git…
31 To get started, see [Requirements](#requirements) and
32 [Installation](#installation). See [Usage](#usage) for a full example and the
35 It may also help to read the [Google Test documentation](https://github.com/google/googletest/blob/…
40 [Discussion group](https://groups.google.com/d/forum/benchmark-discuss)
49 [Building and installing Python bindings](docs/python_bindings.md)
53 The library can be used with C++03. However, it requires C++11 to build,
54 including compiler and standard library support.
56 The following minimum versions are required to build the library:
[all …]
/external/skia/modules/canvaskit/
DREADME.md4 test dependencies. Recent installations of Node have npm as well.
8 To build with GN, you need to have followed the instructions to download Skia and its deps
11 To compile CanvasKit, you will first need to [download and activate `emscripten`][1] using the
12 script in `//bin/activate-emsdk` (or `//tools/git-sync-deps` which also calls activate-emsdk).
13 This places the associated files in `//third_party/externals/emsdk` and the GN[2] build scripts
18 `//modules/canvaskit/BUILD.gn`.
25 can fail with errors about SSL certificates. <https://github.com/emscripten-core/emsdk/pull/273>
27 See also <https://github.com/emscripten-core/emscripten/issues/9036#issuecomment-532092743>
30 # Compile and Run Local Example
33 # The following installs all npm dependencies and only needs to be when setting up
[all …]

12345678910>>...54