| /aosp_15_r20/external/rust/android-crates-io/crates/pin-project-lite/tests/ui/pin_project/ |
| D | packed.stderr | 2 --> tests/ui/pin_project/packed.rs:3:1
13 …= note: packed structs are only aligned by one byte, and many modern architectures penalize unalig…
16 …ch comes from the expansion of the macro `pin_project` (in Nightly builds, run with -Z macro-backt…
19 --> tests/ui/pin_project/packed.rs:3:1
30 …= note: packed structs are only aligned by one byte, and many modern architectures penalize unalig…
33 …ch comes from the expansion of the macro `pin_project` (in Nightly builds, run with -Z macro-backt…
36 --> tests/ui/pin_project/packed.rs:3:1
47 …= note: packed structs are only aligned by one byte, and many modern architectures penalize unalig…
50 …ch comes from the expansion of the macro `pin_project` (in Nightly builds, run with -Z macro-backt…
53 --> tests/ui/pin_project/packed.rs:11:1
[all …]
|
| /aosp_15_r20/external/rust/android-crates-io/crates/grpcio-sys/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 …]
|
| /aosp_15_r20/external/grpc-grpc/tools/run_tests/ |
| H A 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 …]
|
| /aosp_15_r20/external/wycheproof/ |
| H A D | README.md | 14 Project Wycheproof tests crypto libraries against known attacks. It is developed
18 At Google, we rely on many third party cryptographic software libraries.
28 of unit tests that detect known weaknesses or check for expected behaviors of
29 some cryptographic algorithm. Project Wycheproof provides tests for most
37 While we are committed to develop as many attacks as possible, Project
38 Wycheproof is by no means complete. Passing the tests does not imply that the
40 Project Wycheproof tests for. Cryptographers are also constantly discovering
50 Project Wycheproof has tests for the most popular crypto algorithms, including
62 The tests detect whether a library is vulnerable to many attacks, including
67 - And many more -- we have over 80 test cases
[all …]
|
| /aosp_15_r20/external/curl/tests/ |
| H A D | runtests.md | 14 runtests.pl - run one or more test cases
18 **runtests.pl [options] [tests]**
28 Specify which test(s) to run by specifying test numbers or keywords.
30 If no test number or keyword is given, all existing tests that the script can
31 find are considered for running. You can specify single test cases to run by
33 specify a range of tests like `45 to 67`.
35 Specify tests to not run with a leading exclamation point, like `!66`, which
36 runs all available tests except number 66.
38 Prefix a test number with a tilde (~) to still run it, but ignore the results.
40 It is also possible to specify tests based on a keyword describing the test(s)
[all …]
|
| /aosp_15_r20/external/skia/site/docs/dev/testing/ |
| H A 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 …]
|
| /aosp_15_r20/external/igt-gpu-tools/ |
| H A D | NEWS | 32 dropping the audio tests that required exotic custom hardware to
42 And many other bug fixes, improvements, cleanups and new tests.
99 - kms_frontbuffer_tracking no longer tests sink crc. (Dhinakaran Pandiyan)
104 And many other bug fixes, improvements, cleanups and new tests.
129 - Moved handling of a "cork" BO into lib from various tests.
153 And many other bug fixes, improvements, cleanups and new tests.
212 And many other bug fixes, improvements, cleanups and new tests.
250 - Converted remaining shell-script tests to C code (Abdiel Janulgue)
252 - Multiple new tests.
255 And many other bug fixes and improvements.
[all …]
|
| H A D | README.md | 8 drivers. There are many macro-level test suites that get used against the
10 those can be difficult to track down to kernel changes, and many require
12 results. Therefore, IGT GPU Tools includes low-level tools and tests
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
26 Note that a few other microbenchmarks are in tests (like gem_gtt_speed).
28 **tests/**
30 This is a set of automated tests to run against the DRM to validate
31 changes. Many of the tests have subtests, which can be listed by using
32 the --list-subtests command line option and then run using the
[all …]
|
| /aosp_15_r20/external/autotest/docs/ |
| H A D | faft-design-doc.md | 14 - [VBoot_Reference Library Tests](#vboot-reference-library-tests)
15 - [U-Boot vbexport/vboot Tests](#u-boot-vbexport-vboot-tests)
35 …rce.com/chromiumos/third_party/autotest/+/refs/heads/main/docs/faft-how-to-run-doc.md) ([Google s…
43 …ant; however, our current firmware is lack of automated tests. It only relies on the manual tests …
49 - Easy to integrate to our existing test infrastructure, i.e. deploy to test lab, run remotely, con…
63 …many) APIs which the main control logic is used. VBoot export APIs are the most, e.g., TPM, displa…
69 …tests are mostly focused on VBoot Bootstub and VBoot Main Firmware since they are complicated and …
75 <a name="vboot-reference-library-tests" />
80 Source: src/platform/vboot_reference/tests
82 …boot_reference provides a lot of tests varying from crypto algorithms to vboot main logic and cont…
[all …]
|
| /aosp_15_r20/external/linux-kselftest/tools/testing/selftests/arm64/fp/ |
| H A D | README | 1 This directory contains a mix of tests integrated with kselftest and
2 standalone stress tests.
4 kselftest tests
10 Running the non-kselftest tests
60 Ideally, the test should be allowed to run for many minutes or hours
68 should be run in parallel in two KVM guests, while simultaneously
73 $ lkvm run --console=virtio -pconsole=hvc0 --sve Image
81 or until the guest terminates. It is therefore recommended to run
83 allows multiple guests to be run in parallel while running other
95 Again, the test should be allowed to run for many minutes or hours to
|
| /aosp_15_r20/libcore/tools/testmapping/ |
| H A D | README | 1 These scripts help generate the libcore TEST_MAPPING smoke tests, i.e. a set of
2 tests to run on every change, chosen to run as many as possible in less than
7 2. Run the CtsLibcoreTestCases tests to generate logs to extract timings from.
15 you to pick the runs you want. (If you prefer, you can run this after each
16 run, rather than once after all three runs.)
18 6. Check stdout from the script looks okay (not too many warnings, sensible
|
| /aosp_15_r20/external/ltp/pan/cgi/ |
| H A 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.
|
| /aosp_15_r20/external/googletest/ |
| H A D | README.md | 57 Googletest automatically discovers and runs your tests, eliminating the need
58 to manually register your tests
64 write tests that are specific to your code
65 * Death tests: \
66 Googletest supports death tests, which verify that your code exits in a
70 non-fatal with Googletest, allowing tests to continue running even if a
72 * Value-parameterized tests: \
73 Googletest supports value-parameterized tests, which run multiple times with
76 * Type-parameterized tests: \
77 Googletest also supports type-parameterized tests, which run with different
[all …]
|
| /aosp_15_r20/external/cronet/third_party/googletest/src/ |
| H A D | README.md | 61 Googletest automatically discovers and runs your tests, eliminating the need
62 to manually register your tests
68 write tests that are specific to your code
69 * Death tests: \
70 Googletest supports death tests, which verify that your code exits in a
74 non-fatal with Googletest, allowing tests to continue running even if a
76 * Value-parameterized tests: \
77 Googletest supports value-parameterized tests, which run multiple times with
80 * Type-parameterized tests: \
81 Googletest also supports type-parameterized tests, which run with different
[all …]
|
| /aosp_15_r20/external/cronet/third_party/boringssl/src/third_party/googletest/ |
| H A D | README.md | 61 Googletest automatically discovers and runs your tests, eliminating the need
62 to manually register your tests
68 write tests that are specific to your code
69 * Death tests: \
70 Googletest supports death tests, which verify that your code exits in a
74 non-fatal with Googletest, allowing tests to continue running even if a
76 * Value-parameterized tests: \
77 Googletest supports value-parameterized tests, which run multiple times with
80 * Type-parameterized tests: \
81 Googletest also supports type-parameterized tests, which run with different
[all …]
|
| /aosp_15_r20/external/mesa3d/src/broadcom/ci/ |
| H A D | broadcom-rpi3-flakes.txt | 24 # Sometimes fail when run along with other tests, never when run by themselves
43 # Updated by ci-collate, found in this job run: https://gitlab.freedesktop.org/mesa/mesa/-/jobs/561…
46 spec@arb_vertex_buffer_object@vbo-subdata-many drawarrays
47 spec@arb_vertex_buffer_object@vbo-subdata-many drawelements
48 spec@arb_vertex_buffer_object@vbo-subdata-many drawrangeelements
50 # Nightly run expectations update
|
| /aosp_15_r20/external/llvm/docs/ |
| H A D | GettingStartedVS.rst | 15 There are many different projects that compose LLVM. The first piece is the
18 bitcode optimizer. It also contains basic regression tests that can be used to
27 The last major part of LLVM, the execution Test Suite, does not run on Windows,
42 Any system that can adequately run Visual Studio 2013 is fine. The LLVM
55 If you would like to run the LLVM tests you will need `Python
122 or run it from the command line. The program will print the
129 * You can run LLVM tests by merely building the project "check". The test
134 * The LLVM tests can be run by changing directory to the llvm source
144 see many unsupported tests and expected failures.
146 A specific test or test directory can be run with:
[all …]
|
| /aosp_15_r20/external/python/cpython2/Misc/ |
| D | README.valgrind | 20 many allocations (and frees), except for those that are forwarded
22 makes Python run much slower, especially when running under Valgrind.
23 You may need to run the tests in batches under Valgrind to keep
24 the memory usage down to allow the tests to complete. It seems to take
25 about 5 times longer to run --without-pymalloc.
31 This causes many spurious warnings, so it's easier to just skip it.
47 many errors like:
59 time, regardless of how many memory areas are under pymalloc's
|
| /aosp_15_r20/external/libaom/ |
| H A D | README.md | 22 - [Unit tests](#unit-tests)
23 - [Example tests](#example-tests)
24 - [Encoder tests](#encoder-tests)
25 - [IDE hosted tests](#ide-hosted-tests)
30 - [Running tests directly](#running-test_libaom-directly)
31 - [Running tests via CMake](#running-the-tests-via-the-cmake-build)
55 recommended. A C++ compiler is necessary to build the unit tests and some
82 CMake replaces the configure step typical of many projects. Running CMake will
96 run the generated build will use cc and c++ by default.
100 The AV1 codec library has a great many configuration options. These come in two
[all …]
|
| /aosp_15_r20/external/angle/doc/ |
| H A D | CaptureAndReplay.md | 7 * GLES capture has many unimplemented functions.
10 * Mid-execution capture has many unimplemented features.
76 To run a sample replay you can use a template located in
77 [samples/capture_replay](../samples/capture_replay). First run your sample and ensure all capture
86 See [samples/BUILD.gn](../samples/BUILD.gn) for details. Then build and run your replay sample:
95 To run your capture on any platform (Windows, Linux, Android, Mac (untested)), you'll need to
98 Create a folder under `src/tests/restricted_traces` that matches the `ANGLE_CAPTURE_LABEL` you
103 src/tests/restricted_traces$ ls -1 desktop_test/
114 [restricted_traces.json](../src/tests/restricted_traces/restricted_traces.json).
121 Now you should be able to compile and run the perf test including your trace:
[all …]
|
| /aosp_15_r20/external/zstd/tests/regression/ |
| H A D | README.md | 1 # Regression tests
3 The regression tests run zstd in many scenarios and ensures that the size of the compressed results…
5 These tests get run every night by CircleCI. If the job fails you can read the diff printed by the …
9 From the root of the zstd repo run:
17 cd tests/regression
|
| /aosp_15_r20/external/ltp/ |
| H A D | runltp | 127 … [NUM_FILES = Write() to these many files (Defaults to 1 when value 0 or undefined)]
128 … [NUM_BYTES = write these many bytes (defaults to 1GB, when value 0 or undefined)]
132 …-F LOOPS,PERCENTAGE Induce PERCENTAGE Fault in the Kernel Subsystems, and, run each test for LOOPS…
143 … [CHUNKS = malloc these many chunks (default is 1 when value 0 or undefined)]
150 -N Run all the networking tests.
168 -b DEVICE Some tests require an unmounted block device
169 to run correctly.
171 -z BIG_DEVICE Some tests require a big unmounted block device
172 to run correctly.
441 result of concurrently running multiple tests designed
[all …]
|
| /aosp_15_r20/external/python/cpython3/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
|
| /aosp_15_r20/external/cronet/third_party/lss/ |
| H A D | README.md | 51 The linux\_syscall\_support.h header provides many knobs for you to control
75 trying to run on older kernels, you will need to handle errors yourself (e.g.
79 flag was added to many syscalls, but if you try to run use it on older kernels,
118 Tests are found in the [tests/](./tests/) subdirectory. It does not (yet) offer
121 New commits that update/change/add syscall wrappers should include tests for
122 them too. Consult the [test documentation](./tests/README.md) for more details.
124 To run, just run `make` inside the tests directory. It will compile & execute
125 the tests locally.
127 There is some limited cross-compile coverage available if you run `make cross`.
138 LSS changes don't run into problems with updating `lss_revision`.
|
| /aosp_15_r20/external/ltp/testcases/network/stress/ |
| H A D | README | 7 These tests require two machines. And each machine needs to have 2 or more
8 interfaces. These tests assume that they run on the following topology.
24 Test Links are the place where the stress tests run. For example, test packets
26 the interfaces connected to the test links would be changed by the tests.
38 Like the other network tests, the remote host must have the LTP installed
47 To run the network stress testcases, use network.sh script, located in
51 Some stress tests originally designed to be tested with rsh for accessing
55 The behaviour of network stress tests is configurable with environment
59 Attention for HTTP/FTP stress tests
62 When you run http or ftp stress tests, you have to start http or ftp server
[all …]
|