Searched +refs:run +refs:many +refs:tests (Results 1 – 25 of 534) sorted by relevance
12345678910>>...22
| /third_party/grpc/tools/run_tests/ |
| D | README.md | 3 This directory contains scripts that facilitate building and running tests. We are using python scr…
4 tests because that gives us the opportunity to run tests using the same commandline regardless of t…
6 # Unit tests (run_tests.py)
8 Builds gRPC in given language and runs unit tests. Use `tools/run_tests/run_tests.py --help` for mo…
13 ###### Useful options (among many others)
14 …ontainer containing all the prerequisites for given language and runs the tests under that contain…
15 - `--build_only` Only build, do not run the tests.
19 Note: some tests may be flaky. Check the "Issues" tab for known flakes and other issues.
21 The full suite of unit tests will take many minutes to run.
23 # Interop tests (run_interop_tests.py)
[all …]
|
| /third_party/boost/libs/iterator/test/ |
| D | Jamfile.v2 | 7 # These first two tests will run last, and are expected to fail
8 # for many less-capable compilers.
13 [ run is_convertible_fail.cpp ]
15 [ run zip_iterator_test.cpp
21 [ run zip_iterator_test2_std_tuple.cpp ]
22 [ run zip_iterator_test2_fusion_vector.cpp ]
23 [ run zip_iterator_test2_fusion_list.cpp ]
24 # [ run zip_iterator_test2_fusion_deque.cpp ] // See bug report for fusion https://svn.boost.org…
25 [ run zip_iterator_test_fusion.cpp ]
26 [ run zip_iterator_test_std_tuple.cpp ]
[all …]
|
| /third_party/ltp/pan/cgi/ |
| D | README | 10 <host> The hostname the tests were run on
17 summary - a very brief table listing how many tests passed,
18 failed, didn't run, etc. This wasn't released.
33 to compare as many results as you want, side by side. Also, I started
46 before running the tests. I use this information to display the `uname
48 information, but the scripts should still run.
|
| /third_party/skia/site/docs/dev/testing/ |
| D | testing.md | 16 When you run this, you may notice your CPU peg to 100% for a while, then taper
17 off to 1 or 2 active cores as the run finishes. This is intentional. DM is very
19 forced to run on a single thread. You can use `--threads N` to limit DM to N
30 492 srcs * 3 sinks + 382 tests == 1858 tasks
54 supports many test configurations, which are not all appropriate for all
55 machines. These lines are a sort of FYI, mostly in case DM can't run some
56 configuration you might be expecting it to run.
65 492 srcs * 3 sinks + 382 tests == 1858 tasks
68 DM has found 382 unit tests (code linked in from tests/), and 492 other drawing
69 sources. These drawing sources may be GM integration tests (code linked in from
[all …]
|
| /third_party/flutter/skia/site/dev/testing/ |
| D | testing.md | 14 When you run this, you may notice your CPU peg to 100% for a while, then taper
15 off to 1 or 2 active cores as the run finishes. This is intentional. DM is
17 still forced to run on a single thread. You can use `--threads N` to limit DM to
26 492 srcs * 3 sinks + 382 tests == 1858 tasks
49 supports many test configurations, which are not all appropriate for all
50 machines. These lines are a sort of FYI, mostly in case DM can't run some
51 configuration you might be expecting it to run.
59 492 srcs * 3 sinks + 382 tests == 1858 tasks
62 DM has found 382 unit tests (code linked in from tests/), and 492 other drawing
63 sources. These drawing sources may be GM integration tests (code linked in
[all …]
|
| /third_party/boost/libs/hof/ |
| D | README.md | 6 …at provides utilities for functions and function objects, which can solve many problems with much …
11 …lement a functional language in C++. As such, HigherOrderFunctions solves many problems relevant t…
40 Both MSVC and gcc 4.6 have limited constexpr support due to many bugs in the implementation of cons…
45 On older compilers such as gcc 4.6 and gcc 4.7, `noexcept` is not used due to many bugs in the impl…
50 …tions library uses cmake to build. To configure with cmake create a build directory, and run cmake:
59 To install the library just run the `install` target:
66 The tests can be built and run by using the `check` target:
70 The tests can also be ran using Boost.Build, just copy library to the boost source tree, and then:
|
| /third_party/boost/libs/test/doc/introduction/ |
| D | overview.qbk | 10 Unit testing tasks arise during many different stages of software development: from initial project
13 domain cause many requirements (sometimes conflicting) to be placed on a unit testing framework. Th…
17 * The framework should allow advanced users to perform non-trivial tests.
18 * Test module should be able to have many small test cases and developer should be able to group th…
21 * During the regression testing users just want to know if any tests failed.
23 to compile a test that takes a second to run.
24 * For long and complex tests users want to be able to see the testing progress.
25 * Simplest tests shouldn't require an external library.
58 …the code under tested. For details, see section [link boost_test.testing_tools Writing unit tests].
62 * You can control the run-time behavior of the built test module (e.g., run only selected tests, ch…
|
| /third_party/boost/libs/predef/test/ |
| D | build.jam | 29 [ run info_as_cpp.cpp : : : <test-info>always_show_run_output ]
30 [ run info_as_c.c : : : <test-info>always_show_run_output ]
31 [ run info_as_objcpp.mm : : : <test-info>always_show_run_output ]
32 [ run info_as_objc.m : : : <test-info>always_show_run_output ]
33 [ run version.cpp ]
34 [ run make.cpp ]
37 [ run check_value.cpp : : : <test-info>always_show_run_output
39 [ run workaround.cpp ]
41 [ run tested_at.cpp ]
47 # we don't have many we can just do all of them.
[all …]
|
| /third_party/node/test/ |
| D | README.md | 5 For a detailed guide on how to write tests in this
6 directory, see [the guide on writing tests](../doc/guides/writing-tests.md).
8 On how to run tests in this directory, see
11 For the tests to run on Windows, be sure to clone Node.js source code with the
19 …[addon](https://nodejs.org/api/addons.html) functionality along with some tests that require an ad…
22 | `cctest` | Yes | C++ tests that are run as part of the build process. |
24 | `common` | | Common modules shared among many tests. [Documentation](./common/R…
27 | `fixtures` | | Test fixtures used in various tests throughout the test suite…
28 …rking related modules may also be present in other directories, but those tests do not make outbou…
30 | `known_issues` | Yes | Tests reproducing known issues within the system. All tests inside…
[all …]
|
| /third_party/cef/tools/distrib/mac/ |
| D | README.standard.txt | 7 components required to run the debug version of CEF-based
16 components required to run the release version of CEF-based
19 tests/ Directory of tests that demonstrate CEF usage.
29 ceftests Contains unit tests that exercise the CEF APIs.
41 CMake can be used to generate project files in many different formats. See
|
| /third_party/skia/third_party/externals/angle2/doc/ |
| D | CaptureAndReplay.md | 7 * GLES capture has many unimplemented functions.
10 * Mid-execution capture has many unimplemented features.
88 To run a CPP replay you can use a template located in
89 [samples/capture_replay](../samples/capture_replay). First run your capture and ensure all capture
97 See [samples/BUILD.gn](../samples/BUILD.gn) for details. Then build and run your replay sample:
155 we've run go as high as ID 6.
163 Until we have samples building for Android, the replay sample must be run on desktop.
164 We will also be plumbing replay files into perf and correctness tests which will run on Android.
201 A job unit is a test batch. Each test has to go through 3 stages: capture run, replay build, and
202 replay run. The test batch batches the replay build stage of multiple tests together, and the
[all …]
|
| /third_party/ltp/testcases/open_posix_testsuite/stress/timers/ |
| D | plan.txt | 33 - Repeat key functional tests multiple times.
37 - Send many (1000s) of signals at the same time.
41 - Set memory to 95% and run through key clocks functions.
42 - Set memory to 95% and run through key timers functions.
46 - Set CPU to 95% and run through key clocks functions.
47 - Set CPU to 95% and run through key timers functions.
51 - Set up >10,000 timers and run through key clocks functions.
52 - Set up >10,000 timers and run through key timers functions.
54 * Will also perform kernel profiling on select stress tests.
|
| /third_party/ltp/ |
| D | README.md | 6 project goal is to deliver tests to the open source community that validate the
31 **Be careful with these tests!**
33 Don't run them on production systems. Growfiles, doio, and iogen in particular
37 Quick guide to running the tests
60 the whole LTP, if you want to run a syscall testcase following should work.
87 $ ./foo_1-1.run-test
103 Some tests will be disabled if the configure script can not find their build
108 * If a tests fails due to a missing user or group, see the Quick Start section
111 Running tests
114 To run all the test suites
[all …]
|
| /third_party/node/doc/guides/ |
| D | maintaining-the-build-files.md | 9 There are three main build files that may be directly run when building Node.js:
21 * `Makefile`: A Makefile that can be run with GNU Make. It provides a set of
23 documentation, and interact with the CI to run benchmarks or tests. For a
27 Node.js binary, on other systems `configure` must be run manually before running
32 To see the help text, run `.\vcbuild help`. Update this file when you need to
37 The `configure` script recognizes many CLI flags for special build formulas.
45 To see the help text, run `python configure --help`. Update this file when you
50 To see the help text, run `make help`. This file is not generated, it is
51 maintained by humans. This is not usually run on Windows, where
57 targets, the parallel tests will take up all the available cores, regardless
|
| /third_party/python/Misc/ |
| D | README.valgrind | 24 many allocations (and frees), except for those that are forwarded
26 makes Python run much slower, especially when running under Valgrind.
27 You may need to run the tests in batches under Valgrind to keep
28 the memory usage down to allow the tests to complete. It seems to take
29 about 5 times longer to run --without-pymalloc.
35 This causes many spurious warnings, so it's easier to just skip it.
55 many errors like:
67 time, regardless of how many memory areas are under pymalloc's
|
| /third_party/node/deps/npm/node_modules/nopt/ |
| D | CHANGELOG.md | 6 Merged so many patches at once that the code fencing
43 Only run Windows tests on Windows, only run Unix tests on a Unix.
46 Refresh Travis to run the tests against the currently-supported batch of npm
|
| /third_party/selinux/ |
| D | README.md | 30 * and many more (https://repology.org/project/policycoreutils/versions)
95 To build and install everything under a private directory, run:
103 To run tests with the built libraries and programs, several paths (relative to `$DESTDIR`) need to …
108 Some tests require the reference policy to be installed (for example in `python/sepolgen`).
109 In order to run these ones, instructions similar to the ones in section `install` of [./.travis.yml…
113 on x86_64, run:
117 or on x86 (32-bit), run:
128 Setting CFLAGS during the make process will cause the omission of many defaults. While the project …
|
| /third_party/mesa3d/docs/ci/ |
| D | docker.rst | 4 For llvmpipe and swrast CI, we run tests in a container containing
15 developer working on them may produce many more images while trying to
20 have tags, so we can have DUT-specific jobs that only run on runners
23 Since dEQP takes a long time to run, we mark the job as "parallel" at
28 To reduce dEQP runtime (or avoid tests with unreliable results), a
29 deqp-runner.sh invocation can provide a list of tests to skip. If
31 failures, and the job will only fail on tests that aren't listed (look
32 at the job's log for which specific tests failed).
42 If the system goes down during a test run, that job will eventually
48 * DUTs must be able to run Docker
[all …]
|
| /third_party/openssl/test/ |
| D | README.external | 13 In order to run the BoringSSL tests with OpenSSL, first checkout the BoringSSL
20 The BoringSSL tests are only confirmed to work at a specific commit in the
30 Configure the OpenSSL source code to enable the external tests:
34 enable-external-tests
36 Note that using other config options than those given above may cause the tests
39 Run the OpenSSL tests by providing the path to the BoringSSL test runner in the
47 To see more detailed output you can run just the BoringSSL tests with the
57 A large number of the BoringSSL tests are known to fail. A test could fail
58 because of many possible reasons. For example:
66 In order to provide a "clean" baseline run with all the tests passing a config
[all …]
|
| /third_party/protobuf/js/ |
| D | README.md | 42 Once you have `protoc` compiled, you can run the tests by typing:
52 This will run two separate copies of the tests: one that uses
55 If all of these tests pass, you know you have a working setup.
69 If you want to use Closure imports, your build should run a command
77 tests the generated files contain many `goog.provide` statements like:
85 The generated code will also `goog.require()` many types in the core library,
86 and they will require many types in the Google Closure library. So make sure
107 If you want to use CommonJS imports, your build should run a command
166 For more examples, see the tests. You can also look at the generated code
|
| /third_party/cef/tools/distrib/linux/ |
| D | README.standard.txt | 6 Debug Contains libcef.so and other components required to run the debug
16 Release Contains libcef.so and other components required to run the release
25 tests/ Directory of tests that demonstrate CEF usage.
35 ceftests Contains unit tests that exercise the CEF APIs.
47 CMake can be used to generate project files in many different formats. See
|
| /third_party/cef/tools/distrib/win/ |
| D | README.standard.txt | 7 build and run the debug version of CEF-based applications. By
17 build and run the release version of CEF-based applications. By
25 tests/ Directory of tests that demonstrate CEF usage.
35 ceftests Contains unit tests that exercise the CEF APIs.
47 CMake can be used to generate project files in many different formats. See
|
| /third_party/skia/third_party/externals/dawn/docs/ |
| D | testing.md | 14 A Chromium checkout is required for the highest optimization flags. It is possible to build and run…
19 …- Step: A group of Iterations run together. The number of `iterationsPerStep` is provided to the c…
20 …- Trial: A group of Steps run consecutively. `kNumTrials` are run for each test. A Step in a Trial…
22 (See [`//src/tests/perf_tests/DawnPerfTest.h`](https://cs.chromium.org/chromium/src/third_party/daw…
41 …hromium/src/third_party/dawn/scripts/perf_test_runner.py) may be run to continuously run a test an…
59 DrawCallPerf tests drawing a simple triangle with many ways of encoding commands,
68 - Static/Dynamic data: Updating data for each draw is a common use case. It also tests
|
| /third_party/ltp/testcases/open_posix_testsuite/scripts/ |
| D | locate-test | 13 Lists the tests (source/binary) available from the DIRECTORY directory
16 --buildonly List only tests that require building
17 --runnable List only tests that are executable
18 If you just want to build a test, but not run it,
35 not support TESTs compiled from many different sources.
|
| /third_party/flutter/skia/third_party/externals/wuffs/doc/ |
| D | benchmarks.md | 6 "Mimic" tests check that Wuffs' output mimics (i.e. exactly matches) other
27 configuration or installation. For example, to run the `std/zlib` benchmarks:
35 A comment near the top of that .c file says how to run the mimic benchmarks.
41 code change. To install it, first install Go, then run `go get
47 As mentioned above, individual benchmark programs can be run manually. However,
48 the canonical way to run the benchmarks (across multiple compilers and multiple
80 The 1k, 10k, etc. numbers are approximately how many bytes there in the decoded
112 The 1k, 10k, etc. numbers are approximately how many bytes of pixel data there
|
12345678910>>...22