Home
last modified time | relevance | path

Searched +full:build +full:- +full:tests (Results 1 – 25 of 1087) sorted by relevance

12345678910>>...44

/third_party/mesa3d/.gitlab-ci/build/
Dgitlab-ci.yml2 .build-common:
3 extends: .container+build-rules
7 # Build jobs don't take more than 1-3 minutes. 5-8 min max on a fresh runner
22 - _build/meson-logs/*.txt
23 - _build/meson-logs/strace
24 - _build/.ninja_log
25 - artifacts
28 .build-linux:
29 extends: .build-common
36 - !reference [default, before_script]
[all …]
/third_party/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
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 …]
/third_party/mbedtls/tests/scripts/
Dall.sh6 # SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-or-later
15 # -------
17 # To run all tests possible or available on the platform.
20 # ---------------
22 # Warning: the test is destructive. It includes various build modes and
26 # * Makefile, library/Makefile, programs/Makefile, tests/Makefile,
32 # * Basic Unix tools (Windows users note: a Unix-style find must be before
39 # * arm-gcc and mingw-gcc
40 # * ArmCC 5 and ArmCC 6, unless invoked with --no-armcc
42 # interoperability tests. The following are the official versions at the
[all …]
/third_party/jerryscript/docs/
D00.GETTING-STARTED.md7 - `gcc` or any C99-compliant compiler (native or cross, e.g., arm-none-eabi)
8 - `cmake` >= `2.8.12.2`
12 - `bash` >= `4.3.11`
13 - `cppcheck` >= `1.61`
14 - `vera++` >= `1.2.1`
15 - `python` >= `2.7.6`
18 sudo apt-get install gcc gcc-arm-none-eabi cmake cppcheck vera++ python
23 - `awk`
24 - `bc`
25 - `find`
[all …]
/third_party/grpc/tools/buildgen/
Dextract_metadata_from_bazel_xml.py8 # http://www.apache.org/licenses/LICENSE-2.0
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
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:
29 # TODO(jtattermusch): In the future we want to get rid of the legacy build.yaml
30 # format entirely or simplify it to a point where it becomes self-explanatory
[all …]
/third_party/skia/m133/modules/canvaskit/
DREADME.md3 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
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>
38 make local-example
45 For other available build targets, see `Makefile` and `compile.sh`.
46 For example, building a stripped-down version of CanvasKit with no text support or
[all …]
/third_party/skia/third_party/externals/swiftshader/docs/
DdEQP.md7 -------------
13 5. Install [MinGW-W64](http://mingw-w64.org/doku.php/download)
15 6. Install [Git](https://git-scm.com/download/win)
18 9. Set environment variables: Config Panel -> System and Security -> System -> Advanced system sett…
20 * Add `<path to MinGW-W64>\bin` to your PATH environment variable
23 … is in the Android SDK, typically in `C:\Users\<username>\AppData\Local\Android\sdk\platform-tools`
28 ----------------
32 `git clone https://github.com/KhronosGroup/VK-GL-CTS`
34 You may wish to check out a stable vulkan-cts-* branch.
49 -----------------
[all …]
/third_party/rust/crates/regex/.github/workflows/
Dci.yml6 - master
8 - cron: '00 01 * * *'
10 # The section is needed to drop write-all permissions that are granted on
16 # on pull-requests, etc. may need additional permissions:
19 # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
21 # Reference for how to assign permissions on a job-by-job basis:
22 # https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
25 # https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for…
34 # For some builds, we use cross to test on 32-bit and big-endian
37 # When CARGO is set to CROSS, TARGET is set to `--target matrix.target`.
[all …]
/third_party/grpc/tools/remote_build/
DREADME.md3 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 …build & execution platform. If you want to run tests on linux, you need to run bazel from a linux …
26 # manual run of bazel tests remotely on Foundry
27 bazel --bazelrc=tools/remote_build/linux.bazelrc test --config=opt //test/...
32 # manual run of bazel tests remotely on Foundry with given sanitizer
[all …]
Dlinux.bazelrc8 # http://www.apache.org/licenses/LICENSE-2.0
16 # bazelrc file for running gRPC tests with RBE (on Linux)
20 # Next section is linux-specific RBE configuration
21 build --crosstool_top=//third_party/toolchains:rbe_linux_default_toolchain_suite
22 build --extra_toolchains=//third_party/toolchains:rbe_linux_default_cc_toolchain
24 build --extra_execution_platforms=//third_party/toolchains:rbe_linux_default_platform
25 build --host_platform=//third_party/toolchains:rbe_linux_default_platform
26 build --platforms=//third_party/toolchains:rbe_linux_default_platform
28 # we assume the default bazel RBE build is on linux,
30 build --test_tag_filters=-no_linux
[all …]
/third_party/jerryscript/
D.travis.yml7 # Default job task: run tests as defined in the $OPT environment variable.
9 script: tools/run-tests.py $OPTS
14 - name: "Checks"
16 …- tools/run-tests.py --check-signed-off=travis --check-doxygen --check-vera --check-license --chec…
17 - travis_wait 40 tools/run-tests.py --check-cppcheck
22 - name: "Linux/x86-64 Build, Correctness & Debugger Tests"
24 - OPTS="--quiet --jerry-tests --jerry-test-suite --jerry-debugger"
26 - name: "Linux/x86 (cpointer-32bit) Build & Correctness Tests"
28 …- OPTS="--quiet --jerry-tests --jerry-test-suite --buildoptions=--compile-flag=-m32,--cpointer-32b…
31 packages: [gcc-multilib]
[all …]
/third_party/skia/m133/infra/wasm-common/
DMakefile2 # Set the build context to the current work dir, so we can copy
4 docker build -t gold-karma-chrome-tests -f ./docker/gold-karma-chrome-tests/Dockerfile .
7 # Set the build context to the current work dir, so we can copy
9 docker build -t perf-karma-chrome-tests -f ./docker/perf-karma-chrome-tests/Dockerfile .
12 mkdir -p ./tmp
13 CGO_ENABLED=0 GOOS=linux go build -o ./tmp/gold-aggregator -a ./gold/
14 mkdir -p ./tmp
15 CGO_ENABLED=0 GOOS=linux go build -o ./tmp/perf-aggregator -a ./perf/
18 # docker run karma-chrome-tests /usr/bin/google-chrome-stable --version
22 docker tag gold-karma-chrome-tests gcr.io/skia-public/gold-karma-chrome-tests:${CHROME_VERSION}
[all …]
/third_party/skia/infra/wasm-common/
DMakefile2 # Set the build context to the current work dir, so we can copy
4 docker build -t gold-karma-chrome-tests -f ./docker/gold-karma-chrome-tests/Dockerfile .
7 # Set the build context to the current work dir, so we can copy
9 docker build -t perf-karma-chrome-tests -f ./docker/perf-karma-chrome-tests/Dockerfile .
12 mkdir -p ./tmp
13 CGO_ENABLED=0 GOOS=linux go build -o ./tmp/gold-aggregator -a ./gold/
14 mkdir -p ./tmp
15 CGO_ENABLED=0 GOOS=linux go build -o ./tmp/perf-aggregator -a ./perf/
18 # docker run karma-chrome-tests /usr/bin/google-chrome-stable --version
22 docker tag gold-karma-chrome-tests gcr.io/skia-public/gold-karma-chrome-tests:${CHROME_VERSION}
[all …]
/third_party/ninja/.github/workflows/
Dlinux.yml10 build:
11 runs-on: [ubuntu-latest]
15 - uses: actions/checkout@v2
16 - uses: codespell-project/actions-codespell@master
19 - name: Install dependencies
21 … curl -L -O https://github.com/Kitware/CMake/releases/download/v3.16.4/cmake-3.16.4-Linux-x86_64.sh
22 chmod +x cmake-3.16.4-Linux-x86_64.sh
23 ./cmake-3.16.4-Linux-x86_64.sh --skip-license --prefix=/usr/local
24 …curl -L -O https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/7/x86_64/Packages/p/p…
25 …curl -L -O https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/7/x86_64/Packages/p/p…
[all …]
/third_party/zlib/contrib/dotzlib/
Dreadme.txt8 --------------------
10 LICENSE_1_0.txt - License file.
11 readme.txt - This file.
12 DotZLib.chm - Class library documentation
13 DotZLib.build - NAnt build file
14 DotZLib.sln - Microsoft Visual Studio 2003 solution file
16 DotZLib\*.cs - Source files for the class library
18 Unit tests:
19 -----------
20 The file DotZLib/UnitTests.cs contains unit tests for use with NUnit 2.1 or higher.
[all …]
/third_party/optimized-routines/string/
DDir.mk1 # Makefile fragment - requires GNU make
3 # Copyright (c) 2019-2021, Arm Limited.
4 # SPDX-License-Identifier: MIT OR Apache-2.0 WITH LLVM-exception
7 B := build/string
10 all-string bench-string check-string install-string clean-string:
15 string-lib-srcs := $(wildcard $(S)/$(ARCH)/*.[cS])
16 string-lib-srcs += $(wildcard $(S)/$(ARCH)/experimental/*.[cS])
17 string-test-srcs := $(wildcard $(S)/test/*.c)
18 string-bench-srcs := $(wildcard $(S)/bench/*.c)
20 string-arch-include-dir := $(wildcard $(S)/$(ARCH))
[all …]
/third_party/grpc/src/php/docker/
DREADME.md9 ## 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:
36 $ ./src/php/bin/run_all_docker_images.sh grpc-ext php-src
41 $ ./src/php/bin/run_all_docker_images.sh --cmds
44 ## Build and Run Specified Image
[all …]
/third_party/rust/rust/compiler/rustc_codegen_gcc/.github/workflows/
Dci.yml4 - push
5 - pull_request
15 build:
16 runs-on: ubuntu-22.04
19 fail-fast: false
22 - { gcc: "libgccjit.so", extra: "", env_extra: "", artifacts_branch: "master" }
23 …- { gcc: "libgccjit_without_int128.so", extra: "", env_extra: "", artifacts_branch: "master-withou…
24 …- { gcc: "libgccjit12.so", extra: "--no-default-features", env_extra: "TEST_FLAGS='-Cpanic=abort -…
26 "--mini-tests",
27 "--std-tests",
[all …]
/third_party/astc-encoder/Docs/
DTesting.md3 The repository contains a small suite of tests which can be used to sanity
10 Running the tests requires Python 3.7 to be installed on the host machine, and
11 an `astcenc-avx2` release build to have been previously compiled and installed
13 can be achieved by configuring the CMake build using the install prefix
14 `-DCMAKE_INSTALL_PREFIX=../` and then running a build with the `install` build
17 # Running C++ unit tests
19 We support a small (but growing) number of C++ unit tests, which are written
23 To build unit tests pull the `googletest` git submodule and add
24 `-DASTCENC_UNITTEST=ON` to the CMake command line when configuring.
26 To run unit tests use the CMake `ctest` utility from your build directory after
[all …]
/third_party/protobuf/cmake/
DREADME.md1 This directory contains *CMake* files that can be used to build protobuf.
4 [Git](http://git-scm.com), and [Abseil](https://github.com/abseil/abseil-cpp)
6 and newer on both [Windows](#windows-builds) and [Linux](#linux-builds).
8 Most of the instructions will be given using CMake's command-line interface, but
20 cmake . -DCMAKE_CXX_STANDARD=14
21 cmake --build .
24 will build protobuf using C++14 (see [CXX_STANDARD](https://cmake.org/cmake/help/latest/prop_tgt/CX…
28 On Windows, you can build the project from *Command Prompt* and using an
60 Optionally, you will want to download [ninja](https://ninja-build.org/) and add it to your *PATH* v…
75 C:\Path\to\src> git clone -b [release_tag] https://github.com/protocolbuffers/protobuf.git
[all …]
/third_party/typescript/.vscode/
Dtasks.json8 // less annoying if moving up to the new build or going back to
9 // the old build.
11 // This is first because the acutal "npm: build:tests" task
15 "label": "gulp: tests",
17 "script": "build:tests",
18 "group": "build",
28 … "args": ["${workspaceFolder}/lib/tsc.js", "--build", "${workspaceFolder}/src", "--watch"],
29 "group": "build",
32 "$tsc-watch"
36 "label": "npm: build:compiler",
[all …]
/third_party/glfw/
D.gitignore1 # The canonical out-of-tree build subdirectory
2 build
3 build-*
23 GLFW.build
33 build.ninja
79 examples/triangle-opengl
82 tests/*.app
83 tests/*.exe
84 tests/clipboard
85 tests/cursor
[all …]
/third_party/musl/libc-test/
DREADME1 libc-test is developed as part of the musl project
2 http://www.musl-libc.org/
7 build and run tests:
13 a REPORT file that contains all build and runtime errors
14 (this means that make does not stop at build failures)
16 contributing tests:
20 - tests should be easy to run and build even a single test in isolation
22 - failure of one test should not interfere with others
23 (build failure, crash or unexpected results are all failures)
24 - test output should point to the cause of the failure
[all …]
/third_party/vk-gl-cts/external/openglcts/
DREADME.md4 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)
18 - [Test History](#test-history)
[all …]
/third_party/python/Tools/ssl/
Dmultissltests.py2 """Run Python tests against multiple installations of OpenSSL and LibreSSL
14 The script must be run with Python's build directory as current working
23 (c) 2013-2017 Christian Heimes <christian@python.org>
70 "Run CPython tests with multiple OpenSSL and LibreSSL "
75 '--debug',
80 '--disable-ancient',
85 '--openssl',
94 '--libressl',
103 '--tests',
106 help="Python tests to run, defaults to all SSL related tests.",
[all …]

12345678910>>...44