Searched +full:build +full:- +full:and +full:- +full:run +full:- +full:tests (Results 1 – 25 of 1154) sorted by relevance
12345678910>>...47
| /external/ltp/testcases/open_posix_testsuite/Documentation/ |
| D | HOWTO_RunTests | 4 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
13 tests may leave the system in an indeterminate state.
16 ----------------------------------------------------
18 * Conformance Tests
19 The build and execution process varies for conformance tests.
21 For definitions tests, the build and execution process is the same since
[all …]
|
| /external/igt-gpu-tools/ |
| D | README.md | 5 -----------
7 IGT GPU Tools is a collection of tools for development and testing of the DRM
8 drivers. There are many macro-level test suites that get used against the
9 drivers, including xtest, rendercheck, piglit, and oglconform, but failures from
10 those can be difficult to track down to kernel changes, and many require
11 complicated build procedures or specific testing environments to get useful
12 results. Therefore, IGT GPU Tools includes low-level tools and tests
13 specifically for development and testing of the DRM Drivers.
22 The benchmarks require KMS to be enabled. When run with an X Server
23 running, they must be run as root to avoid the authentication
[all …]
|
| /external/skia/modules/canvaskit/ |
| D | README.md | 3 Node v14 or later is required to run tests. We use npm (the Node Package Manager) to install
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 …]
|
| /external/cronet/third_party/libc++/src/docs/ |
| D | TestingLibcxx.rst | 13 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
19 the tests. This guide provides information on how to use LIT directly to
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/apache-xml/test/java/xdocs/sources/tests/ |
| D | getstarted.xml | 3 <!--
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 …]
|
| D | faq.xml | 3 <!--
12 * http://www.apache.org/licenses/LICENSE-2.0
17 * See the License for the specific language governing permissions and
19 -->
27 <li><link anchor="viewresults">Pretty-printing results</link></li>
28 <li><link anchor="debug">Run tests in a debugger, etc.</link></li>
31 <s2 title="Prepare to run tests">
34 cvs checkout xml-xalan/java<br/>
35 cvs checkout xml-xalan/test<br/>
36 cd xml-xalan/java<br/>
[all …]
|
| D | run.xml | 3 <!--
12 * http://www.apache.org/licenses/LICENSE-2.0
17 * See the License for the specific language governing permissions and
19 -->
20 <s1 title="Running Tests">
22 <li><link anchor="how-to-run">How-to: Run Xalan-J tests</link></li>
23 <li><link anchor="how-to-view-results">How-to: View Test Results</link></li>
24 <li><link anchor="test-options">Common Test Options</link></li>
25 <li><link anchor="how-to-run-c">How-to: Run Xalan-C tests</link></li>
28 <anchor name="how-to-run"/>
[all …]
|
| /external/google-fruit/ |
| D | CONTRIBUTING.md | 4 This file contains various information and documentation for Fruit contributors.
7 [here](https://github.com/google/fruit/wiki/install#building-fruit-manually).
13 #### Build systems
15 Fruit supports two build systems: CMake (configured in `CMakeLists.txt` files) and
16 [Bazel](https://www.bazel.io) (configured in `BUILD` files).
18 This means that when you build/test Fruit code you have a choice of what build system you want to u…
20 `CMakeLists.txt` and `BUILD` files, to make sure that Fruit keeps building (and passing its tests) …
22 Both build systems are tested in Travis CI (see below).
24 Example commands to build a development version of Fruit using CMake (with all assertions enabled) …
28 mkdir build-debug
[all …]
|
| /external/deqp/external/openglcts/ |
| D | README.md | 1 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.
7 The Conformance Tests are built on the dEQP framework.
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)
[all …]
|
| /external/pigweed/docs/get_started/ |
| D | upstream.rst | 1 .. _docs-get-started-upstream:
9 :ref:`docs-get-started` if you're looking for instructions on how to use
16 If you haven't already, :ref:`docs-first-time-setup`.
18 -------------
20 -------------
22 of getting setup for Pigweed. If you run into trouble, ensure you've followed
23 all the steps to :ref:`docs-first-time-setup`. The express setup
26 #. **Host** - Mac, Linux, or Windows. Builds and runs tests
27 #. **Device/STM32F429** - Build only; Optionally, the STM32F429I-DISC1 kit to
28 follow along later in the guide to run tests directly on said device(s)
[all …]
|
| /external/grpc-grpc/tools/remote_build/ |
| D | README.md | 3 This allows you to spawn gRPC C/C++ remote build and tests from your workstation with
7 remote build and execution cluster), others will need to rely on local test runs
8 and tests run by Kokoro CI.
13 - See [Installing Bazel](https://docs.bazel.build/versions/master/install.html) for instructions ho…
15 - Setup Application Default Credentials (ADC) for running remote builds by following the ["Set cred…
18 ## Running remote build manually from dev workstation
20 …run the bazel command needs to always match your desired build & execution platform. If you want t…
24 For `opt` or `dbg` run this command:
26 # manual run of bazel tests remotely on Foundry
27 bazel --bazelrc=tools/remote_build/linux.bazelrc test --config=opt //test/...
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/tools/remote_build/ |
| D | README.md | 3 This allows you to spawn gRPC C/C++ remote build and tests from your workstation with
7 remote build and execution cluster), others will need to rely on local test runs
8 and tests run by Kokoro CI.
13 - See [Installing Bazel](https://docs.bazel.build/versions/master/install.html) for instructions ho…
15 - Setup Application Default Credentials (ADC) for running remote builds by following the ["Set cred…
18 ## Running remote build manually from dev workstation
20 …run the bazel command needs to always match your desired build & execution platform. If you want t…
24 For `opt` or `dbg` run this command:
26 # manual run of bazel tests remotely on Foundry
27 bazel --bazelrc=tools/remote_build/linux.bazelrc test --config=opt //test/...
[all …]
|
| /external/swiftshader/docs/ |
| D | dEQP.md | 7 -------------
13 5. Install [MinGW-W64](http://mingw-w64.org/doku.php/download)
15 6. Install [Git](https://git-scm.com/download/win)
16 7. Set environment variables: Config Panel -> System and Security -> System -> Advanced system sett…
18 * Add `<path to MinGW-W64>\bin` to your PATH environment variable
23 ----------------
27 `git clone https://github.com/KhronosGroup/VK-GL-CTS`
29 You may wish to check out a stable vulkan-cts-* branch.
31 13. Get dEQP's dependencies. In your dEQP root directory, open 'cmd' and run:
44 -----------------
[all …]
|
| /external/ltp/android/ |
| D | README.md | 7 ------------
9 [Github](https://github.com/linux-test-project/ltp) (upstream)
11 LTP (Linux Test Project) is a suite of tests that covers both kernel interfaces
12 and userspace functionality (glibc, commonly used binaries, etc). For the
14 and in fact much of it must be disabled, given the functionality is not
17 As of Jan 2023 there are on the order of 1300 tests executed in VTS on arm64.
18 Most tests are run in both 32-bit and 64-bit mode. Many more are available but
21 How is LTP Run in VTS?
22 ----------------------
28 test/vts-testcase/kernel/ltp. Some noteworthy directories/files:
[all …]
|
| /external/openthread/.github/workflows/ |
| D | toranj.yml | 5 # Redistribution and use in source and binary forms, with or without
8 # notice, this list of conditions and the following disclaimer.
10 # notice, this list of conditions and the following disclaimer in the
11 # documentation and/or other materials provided with the distribution.
16 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
17 # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
33 branches-ignore:
34 - 'dependabot/**'
[all …]
|
| D | simulation-1.1.yml | 5 # Redistribution and use in source and binary forms, with or without
8 # notice, this list of conditions and the following disclaimer.
10 # notice, this list of conditions and the following disclaimer in the
11 # documentation and/or other materials provided with the distribution.
16 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
17 # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
33 branches-ignore:
34 - 'dependabot/**'
[all …]
|
| D | simulation-1.2.yml | 5 # Redistribution and use in source and binary forms, with or without
8 # notice, this list of conditions and the following disclaimer.
10 # notice, this list of conditions and the following disclaimer in the
11 # documentation and/or other materials provided with the distribution.
16 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
17 # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
33 branches-ignore:
34 - 'dependabot/**'
[all …]
|
| /external/grpc-grpc/src/php/docker/ |
| D | README.md | 9 ## Build and Run Tests
14 To build all docker images:
19 Or to only build some selected images
21 $ ./src/php/bin/build_all_docker_images.sh grpc-ext php-src
24 Or to only print out individual `docker build` commands
26 $ ./src/php/bin/build_all_docker_images.sh --cmds
29 To run all tests:
34 Or to only run some selected images
36 $ ./src/php/bin/run_all_docker_images.sh grpc-ext php-src
39 Or to only print out individual `docker run` commands
[all …]
|
| /external/vulkan-validation-layers/ |
| D | BUILD.md | 1 # Build Instructions
3 Instructions for building this repository on Linux, Windows, Android, and
8 1. [Contributing](#contributing-to-the-repository)
9 1. [Repository Content](#repository-content)
10 1. [Repository Set-Up](#repository-set-up)
11 1. [Windows Build](#building-on-windows)
12 1. [Linux Build](#building-on-linux)
13 1. [Android Build](#building-on-android)
14 1. [MacOS build](#building-on-macos)
19 your contribution in a fork of this repository in your GitHub account and then
[all …]
|
| /external/ot-br-posix/.github/workflows/ |
| D | build.yml | 5 # Redistribution and use in source and binary forms, with or without
8 # notice, this list of conditions and the following disclaimer.
10 # notice, this list of conditions and the following disclaimer in the
11 # documentation and/or other materials provided with the distribution.
16 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
17 # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
29 name: Build
33 branches-ignore:
[all …]
|
| /external/cronet/components/cronet/android/ |
| D | test_instructions.md | 1 # Testing and debugging Cronet for Android
5 ## Checkout and build
7 See instructions in the [common checkout and
8 build](/components/cronet/build_instructions.md).
10 ## Running tests locally
13 device](/docs/android_build_instructions.md#Plug-in-your-Android-device)
14 steps. Prefer using a device running a userdebug build.
16 Alternatively, you can pass the --x86 flag to `gn` to test on a local emulator
17 -- make sure you substitute `out/Debug` for `out/Debug-x86` in the instructions
20 ### Running Cronet Java unit tests
[all …]
|
| /external/google-breakpad/android/ |
| D | run-checks.sh | 4 # Redistribution and use in source and binary forms, with or without
9 # notice, this list of conditions and the following disclaimer.
11 # copyright notice, this list of conditions and the following disclaimer
12 # in the documentation and/or other materials provided with the
18 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
19 # "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
20 # LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
25 # DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
35 set -o posix
42 . $PROGDIR/common-functions.sh
[all …]
|
| /external/autotest/docs/ |
| D | user-doc.md | 12 Guides for getting to know the package build system we use.
17 ## Autotest and ebuild workflow
22 The rest of this document is going to use some terms and only explain them
27 At a high level, tests are organized in test cases, each test case being either
28 server or client, with one main .py file named the same as the test case, and
30 test, autotest expects tests to be placed in a monolithic file structure
33 - `/client/tests/`
34 - `/client/site_tests/`
35 - `/server/tests/`
36 - `/server/site_tests/`
[all …]
|
| /external/pigweed/pw_unit_test/ |
| D | docs.rst | 1 .. _module-pw_unit_test:
6 .. pigweed-module::
9 .. tab-set::
11 .. tab-item:: mylib_test.cpp
13 .. code-block:: c++
29 .. tab-item:: BUILD.bazel
31 .. code-block:: python
52 .. tab-item:: mylib.cc
54 .. code-block:: c++
69 .. tab-item:: mylib.h
[all …]
|
| /external/bc/scripts/ |
| D | release.sh | 3 # SPDX-License-Identifier: BSD-2-Clause
5 # Copyright (c) 2018-2023 Gavin D. Howard and contributors.
7 # Redistribution and use in source and binary forms, with or without
11 # list of conditions and the following disclaimer.
14 # this list of conditions and the following disclaimer in the documentation
15 # and/or other materials provided with the distribution.
17 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
18 # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
19 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
24 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
[all …]
|
12345678910>>...47