Home
last modified time | relevance | path

Searched refs:running (Results 51 – 75 of 778) sorted by path

12345678910>>...32

/freebsd/contrib/file/
H A Daclocal.m4375 re-running the configure script with MAKE="gmake" (or whatever is
376 necessary). You can also try re-running configure with the
545 # POSIX will say in a future version that running "rm -f" with no argument
550 # To make any issue more visible, cause the running configure to be aborted
H A Dconfigure16461 \printf "%s\n" "running CONFIG_SHELL=$SHELL \$*" >&6
17464 re-running the configure script with MAKE=\"gmake\" (or whatever is
/freebsd/contrib/file/m4/
H A Dlibtool.m4192 # See if we are running on zsh, and set the options that allow our
718 # See if we are running on zsh, and set the options that allow our
1071 # if running on 10.5 or later, the deployment target defaults
1742 # Dr. Hans Ekkehard Plesser reports seeing a kernel panic running configure
6226 ## the running order or otherwise move them around unless you know exactly
6330 # No sense in running all these tests if we already determined that
7396 ## the running order or otherwise move them around unless you know exactly
7691 # No sense in running all these tests if we already determined that
7827 # No sense in running all these tests if we already determined that
7975 ## the running order or otherwise move them around unless you know exactly
[all …]
/freebsd/contrib/file/magic/Magdir/
H A Darchive198 # byte order as the machine running "file" with "cpio archive", and
200 # from the machine running "file" with "byte-swapped cpio archive".
H A Dcoverage66 # raw data after running a program compiled with:
H A Dhp10 # I think the 500 series was the old stack-based machines, running a
H A Dsylk28 # Excel, version probably running on Windows
H A Dvirtual200 >0x18 lelong 1 \b, running
/freebsd/contrib/flex/
H A DChangeLog55 …enable more silent building of tests. When running 'make V=0 check', some compile and link steps …
343 …can now be used for running "make check" tests. Note that none of these scripts has ever been usi…
1900 testwrapper.sh to handle running with a tables file and specifying
4065 this allows running make pdf and make ps to be successful
4228 * tests/README: update instructions for running test suite
H A DNEWS58 *** When running "make check", you can now pas V=0 to silence more of
160 *** When running the test suite, c++ files are compiled with the c++ header inside the flex distrib…
H A DONEWS893 to yield a 1. This caused problems installing or running
/freebsd/contrib/gdtoa/
H A DREADME156 gd_qnan.h, which the makefile generates by running the program whose
/freebsd/contrib/googletest/
H A DCONTRIBUTING.md91 * [Python](https://www.python.org/) v3.6 or newer (for running some of the
H A DREADME.md74 non-fatal with Googletest, allowing tests to continue running even if a
84 * Various options for running tests: \
85 Googletest provides many options for running tests including running
86 individual tests, running tests in a specific order and running tests in
/freebsd/contrib/googletest/docs/
H A Dadvanced.md567 1. A warning is emitted if multiple threads are running when a death test is
1144 You can use these names in [`--gtest_filter`](#running-a-subset-of-the-tests).
1650 Sometimes a function may need to know the name of the currently running test.
1652 the golden file name based on which test is running. The
1655 To obtain a `TestInfo` object for the currently running test, call
1660 // Gets information about the currently running test.
1670 `current_test_info()` returns a null pointer if no test is running. In
1817 running them so that a filter may be applied if needed. Including the flag
1935 is especially useful when running under a debugger: when the test
2386 When running test programs under a debugger, it's very convenient if the
[all …]
H A Dfaq.md157 sub-processes, but not in the parent process. You can think of them as running
339 test failure that should prevent the test from running, it's necessary to
570 `FooTest` case before running any test in the `BarTest` case. This contradicts
621 ## How can my code detect if it is running in a test?
623 If you write code that sniffs whether it's running in a test and does different
635 that), there is no danger in accidentally running it.
H A Dgmock_cook_book.md3193 You can unlock this power by running your test with the `--gmock_verbose=info`
H A Dpkgconfig.md133 and running `pkg-config` again we get
H A Dprimer.md16 tests by running each of them on a different object. When a test fails,
334 running the `DequeueWorks` test.
H A Dquickstart-bazel.md3 This tutorial aims to get you up and running with GoogleTest using the Bazel
H A Dquickstart-cmake.md3 This tutorial aims to get you up and running with GoogleTest using CMake. If
/freebsd/contrib/googletest/docs/reference/
H A Dassertions.md8 failures and allow the current function to continue running, while `ASSERT_`
66 running.
H A Dtesting.md478 `SetUpTestSuite()` before running the first test in the test suite.
485 `TearDownTestSuite()` after running the last test in the test suite.
544 running each individual test.
551 after running each individual test.
737 [Running a Subset of the Tests](../advanced.md#running-a-subset-of-the-tests)
795 running, or `NULL` if no test is running.
802 running, or `NULL` if no test is running.
1308 GoogleTest defines the following functions to help with writing and running
/freebsd/contrib/googletest/googlemock/
H A DCMakeLists.txt125 # gmock_build_tests option to ON. You can do it by running ccmake
126 # or specifying the -Dgmock_build_tests=ON flag when running cmake.
160 # gmock_all_test is commented to save time building and running tests.
/freebsd/contrib/googletest/googletest/
H A DCMakeLists.txt165 # gtest_build_samples option to ON. You can do it by running ccmake
166 # or specifying the -Dgtest_build_samples=ON flag when running cmake.
189 # gtest_build_tests option to ON. You can do it by running ccmake
190 # or specifying the -Dgtest_build_tests=ON flag when running cmake.

12345678910>>...32