Home
last modified time | relevance | path

Searched +refs:run +refs:tests (Results 1 – 25 of 59) sorted by relevance

123

/f-stack/freebsd/contrib/openzfs/tests/
H A DREADME.md35 to sudo(8) to root without a password to run the test.
43 Once the pre-requisites are satisfied simply run the zfs-tests.sh script:
47 Alternately, the zfs-tests.sh script can be run from the source tree to allow
54 $ ./scripts/zfs-tests.sh
70 configuration from a previous test run. This includes
94 -r RUNFILES Run tests in RUNFILES (default: common.run,linux.run)
110 $ /usr/share/zfs/zfs-tests.sh -r my_tests.run
112 Otherwise user can set needed tags to run only specific tests.
125 Runfile: /usr/share/zfs/runfiles/linux.run
142 Test: /usr/share/zfs/zfs-tests/tests/functional/arc/setup (run as root) [00:00] [PASS]
[all …]
/f-stack/dpdk/doc/guides/prog_guide/
H A Dmeson_ut.rst7 This section describes how to run test cases with the DPDK meson build system.
17 * Fast tests.
18 * Performance tests.
19 * Driver tests.
23 These tests can be run using the argument to ``meson test`` as
33 $ meson test --suite DPDK:fast-tests
38 $ meson test --suite fast-tests
44 Test cases are run serially by default for better stability.
48 * ``is_parallel`` is used to run test case either in parallel or non-parallel mode.
58 or config flags, without which the test cases cannot be run. Such test cases
[all …]
/f-stack/freebsd/contrib/zstd/
H A DTESTING.md5 short, medium, and long tests.
9 Short tests run on CircleCI for new commits on every branch and pull request.
10 They consist of the following tests:
13 - `tests/playTests.sh` on x86_64, without the tests on long data (CLI tests)
14 - Small tests (`tests/legacy.c`, `tests/longmatch.c`) on x64_64
18 Medium tests run on every commit and pull request to `dev` branch, on TravisCI.
19 They consist of the following tests:
20 - The following tests run with UBsan and Asan on x86_64 and x86, as well as with
23 - Fuzzer tests: `tests/fuzzer.c`, `tests/zstreamtest.c`, and `tests/decodecorpus.c`
30 Long tests run on all commits to `release` branch,
[all …]
H A DCONTRIBUTING.md17 2. If you've added code that should be tested, add tests.
60 * Note: run local tests to ensure that your changes didn't break existing functionality
69 2. Code Review and CI tests
70 * Ensure CI tests pass:
270 code that you think can be made to run faster.
349 The easiest way to run these CI tests on your own before submitting a PR to our dev branch
382 CI tests run every time a pull request (PR) is created or updated. The exact tests
383 that get run will depend on the destination branch you specify. Some tests take
384 longer to run than others. Currently, our CI is set up to run a short
385 series of tests when creating a PR to the dev branch and a longer series of tests
[all …]
H A Dappveyor.yml1 # Following tests are run _only_ on `release` branch
114 …COPY build\VS2008\bin\%PLATFORM%\%CONFIGURATION%\fuzzer.exe tests\fuzzer_VS2008_%PLATFORM%_%CONFIG…
124 …COPY build\VS2010\bin\%PLATFORM%_%CONFIGURATION%\fuzzer.exe tests\fuzzer_VS2010_%PLATFORM%_%CONFIG…
134 …COPY build\VS2010\bin\%PLATFORM%_%CONFIGURATION%\fuzzer.exe tests\fuzzer_VS2012_%PLATFORM%_%CONFIG…
144 …COPY build\VS2010\bin\%PLATFORM%_%CONFIGURATION%\fuzzer.exe tests\fuzzer_VS2013_%PLATFORM%_%CONFIG…
154 …COPY build\VS2010\bin\%PLATFORM%_%CONFIGURATION%\fuzzer.exe tests\fuzzer_VS2015_%PLATFORM%_%CONFIG…
155 COPY build\VS2010\bin\%PLATFORM%_%CONFIGURATION%\*.exe tests\
173 CD tests &&
185 # The following tests are for regular pushes
187 # There run less tests, for shorter feedback loop
[all …]
/f-stack/freebsd/contrib/openzfs/.github/workflows/
H A Dzfs-tests.yml1 name: zfs-tests-sanity
8 tests:
15 run: |
27 run: |
30 run: |
33 run: |
36 run: |
44 run: |
45 /usr/share/zfs/zfs-tests.sh -v -s 3G -r sanity
48 run: |
H A Dcheckstyle.yaml15 run: |
19 # packages for tests
24 run: |
29 run: |
32 run: |
35 run: |
H A Dzloop.yml8 tests:
17 run: |
28 run: |
31 run: |
34 run: |
37 run: |
45 run: |
47 # run for 20 minutes to have a total runner time of 30 minutes
51 run: |
/f-stack/freebsd/contrib/openzfs/tests/test-runner/bin/
H A Dtest-runner.py.in214 self.run(False)
260 def run(self, dryrun): member in Cmd
427 def run(self, options): member in Test
454 test.run(options.dryrun)
473 self.tests = tests or []
538 del self.tests[self.tests.index(test)]
545 def run(self, options): member in TestGroup
595 self.tests = {}
809 def run(self, options): member in TestRun
829 self.tests[test].run(options)
[all …]
/f-stack/tools/libxo/doc/
H A Dgetting.rst22 the "*master*" branch. To clone a developer tree, run the following
73 will be ready and you'll just need to run "configure", but if you
74 download the source code from svn, then you'll need to run
83 To build libxo, you'll need to set up the build, run the "*configure*"
84 script, run the "*make*" command, and run the regression tests.
126 To run the configure script, change into the "*build*" directory, and
127 run the "*configure*" script. Add any required options to the
153 Once the "*configure*" script is run, build the images using the
161 libxo includes a set of regression tests that can be run to ensure
164 machine. To run the regression tests::
/f-stack/dpdk/doc/guides/tools/
H A Dcomp_perf.rst9 compress tree. User can use multiple cores to run tests on but only
25 tuned system. Comparing the results of the two tests gives information about
48 Set the hexadecimal bitmask of the cores to run on. The corelist is a
53 One lcore is needed for process admin, tests are run on all other cores.
54 To run tests on two lcores, three lcores must be passed to the tool.
H A Dtestbbdev.rst10 bler and sanity tests. Execution of tests can be customized using various
48 Defines test cases to run. If not specified all available tests are run.
66 Fills vector based on turbo_dec_test1.data file and runs all tests
71 *turb_enc_test2.data* file. For both executions all tests are run.
78 Specifies number of lcores to run. If not specified num_lcores is set
87 and bler tests. If not specified iter_max is set to 6.
91 for bler tests. If not specified snr is set to 0 dB.
101 * Validation tests [-c validation]
150 run tests with different set of vector files without giving all of them explicitly.
158 It runs all tests with following vectors:
[all …]
/f-stack/app/redis-5.0.5/
H A Druntest-cluster14 $TCLSH tests/cluster/run.tcl $*
H A Druntest-sentinel14 $TCLSH tests/sentinel/run.tcl $*
/f-stack/freebsd/contrib/openzfs/scripts/
H A Dzfs2zol-patch.sed17 s:usr/src/test/zfs-tests/include:tests/zfs-tests/include:g
18 s:usr/src/test/zfs-tests/runfiles:tests/runfiles:g
19 s:usr/src/test/zfs-tests/tests/functional:tests/zfs-tests/tests/functional:g
20 s:usr/src/test/zfs-tests/tests/perf:tests/zfs-tests/tests/perf:g
21 s:usr/src/test/test-runner/cmd/run.py:tests/test-runner/cmd/test-runner.py:g
/f-stack/freebsd/contrib/openzfs/tests/runfiles/
H A Dsanity.run11 # This run file contains a subset of functional tests which exercise
14 # each to run at most. This provides a convenient way to sanity test a
15 # change before commiting to a full test run which takes several hours.
17 # Approximate run time: 15 minutes
39 [tests/functional/arc]
43 [tests/functional/bootfs]
47 [tests/functional/cache]
56 [tests/functional/casenorm]
415 [tests/functional/exec]
424 [tests/functional/grow]
[all …]
H A Dcommon.run11 # This run file contains all of the common functional tests. When
12 # adding a new test consider also adding it to the sanity.run file
15 # Approximate run time: 4-5 hours
39 [tests/functional/arc]
44 [tests/functional/atime]
48 [tests/functional/bootfs]
54 [tests/functional/btree]
60 [tests/functional/cache]
71 [tests/functional/casenorm]
617 [tests/functional/io]
[all …]
/f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/perf/
H A Dnfs-sample.cfg17 # This file is a sample NFS configuration for the performance tests. To use the
18 # performance tests over NFS you must have:
35 # The user to run the tests as on the client
/f-stack/app/redis-5.0.5/utils/create-cluster/
H A DREADME2 instances configured to run in cluster mode. Its main goal is to allow manual
4 unit tests, for example when a lot of instances are needed in order to trigger
17 2. Use "./create-cluster start" in order to run the instances.
/f-stack/freebsd/contrib/openzfs/config/
H A Dkernel.m414 dnl # Sequential ZFS_LINUX_TRY_COMPILE tests
21 dnl # Parallel ZFS_LINUX_TEST_SRC / ZFS_LINUX_TEST_RESULT tests
135 dnl # Check results of kernel interface tests.
349 *** Please run 'make prepare' inside the kernel source tree.])
481 *** Please run 'make scripts' inside the kernel source tree.])
652 dnl # files for tests which did compile. This is required for
698 dnl # must never depend on the results of previous tests. Each test
717 dnl # $2 - run on success (valid .ko generated)
718 dnl # $3 - run on failure (unable to compile)
788 dnl # $3 - run on success (valid .ko generated)
[all …]
/f-stack/app/redis-5.0.5/deps/lua/test/
H A DREADME1 These are simple tests for Lua. Some of them contain useful code.
2 They are meant to be run to make sure Lua is built correctly and also
/f-stack/dpdk/doc/guides/bbdevs/
H A Dfpga_lte_fec.rst171 VFs are mutually exclusive and cannot run simultaneously.
238 "-c", "--test-cases" : Defines test cases to run. Run all if not specified.
242 "-l", "--num-lcores" : Number of lcores to run (default=16).
271 In addition to the simple turbo decoder and turbo encoder tests, bbdev also provides
272 a range of additional tests under the test_vectors folder, which may be useful. The results
273 of these tests will depend on the FPGA LTE FEC capabilities:
275 * turbo decoder tests:
284 * turbo encoder tests:
302 The ``pf_bb_config`` application notably enables then to run bbdev-test from the VF
H A Dacc100.rst185 "-c", "--test-cases" : Defines test cases to run. Run all if not specified.
189 "-s", "--snr" : SNR in dB used when generating LLRs for bler tests.
191 "-l", "--num-lcores" : Number of lcores to run (default=16).
212 In addition to the simple LDPC decoder and LDPC encoder tests, bbdev also provides
213 a range of additional tests under the test_vectors folder, which may be useful. The results
214 of these tests will depend on the ACC100 5G/4G FEC capabilities which may cause some
224 The ``pf_bb_config`` application notably enables then to run bbdev-test from the VF
H A Dfpga_5gnr_fec.rst172 VFs are mutually exclusive and cannot run simultaneously.
239 "-c", "--test-cases" : Defines test cases to run. Run all if not specified.
243 "-l", "--num-lcores" : Number of lcores to run (default=16).
272 In addition to the simple LDPC decoder and LDPC encoder tests, bbdev also provides
273 a range of additional tests under the test_vectors folder, which may be useful. The results
274 of these tests will depend on the FPGA 5GNR FEC capabilities.
283 The ``pf_bb_config`` application notably enables then to run bbdev-test from the VF
/f-stack/freebsd/contrib/device-tree/scripts/
H A DKbuild.include81 # output directory for tests below
84 # try-run
88 try-run = $(shell set -e; \
100 as-option = $(call try-run,\
106 as-instr = $(call try-run,\
112 cc-option = $(call try-run,\
117 cc-option-yn = $(call try-run,\
127 cc-disable-warning = $(call try-run,\
145 cc-ldoption = $(call try-run,\
150 ld-option = $(call try-run,\
[all …]

123