/freebsd/lib/googletest/tests/gtest/ |
H A D | Makefile | 17 .for death_test in gtest-death-test_ex_catch_test gtest-death-test_ex_nocatch_test 19 ${death_test}.cc: googletest-death-test_ex_test.cc 25 CXXFLAGS.gtest-death-test_ex_catch_test+= \ 28 CXXFLAGS.gtest-death-test_ex_nocatch_test+= \
|
/freebsd/contrib/one-true-awk/bugs-fixed/ |
H A D | system-status.ok2 | 2 death by signal status 265 3 death by signal with core dump status 262
|
/freebsd/contrib/googletest/googletest/test/ |
H A D | BUILD.bazel | 54 "gtest-death-test_ex_test.cc", 73 "googletest-death-test_ex_test.cc", 105 # Tests death tests. 107 name = "googletest-death-test-test", 109 srcs = ["googletest-death-test-test.cc"], 549 # Verifies interaction of death tests and exceptions. 551 name = "googletest-death-test_ex_catch_test", 553 srcs = ["googletest-death-test_ex_test.cc"],
|
/freebsd/crypto/openssh/ |
H A D | ssh-agent.c | 144 time_t death; member 1070 if (id->death == 0) in reaper() 1072 if (now >= id->death) { in reaper() 1078 deadline = (deadline == 0) ? id->death : in reaper() 1079 MINIMUM(deadline, id->death); in reaper() 1375 time_t death = 0; in process_add_identity() local 1389 if (parse_key_constraints(e->request, k, &death, &seconds, &confirm, in process_add_identity() 1433 if (lifetime && !death) in process_add_identity() 1434 death = monotime() + lifetime; in process_add_identity() 1454 id->death = death; in process_add_identity() [all …]
|
/freebsd/contrib/googletest/docs/ |
H A D | faq.md | 131 ## My death test modifies some state, but the change seems lost after the death test finishes. Why? 139 In particular, if you use mocking and the death test statement invokes some mock 258 ## My death test hangs (or seg-faults). How do I fix it? 260 In GoogleTest, death tests are run in a child process and the way they work is 261 delicate. To write death tests you really need to understand how they work—see 262 the details at [Death Assertions](reference/assertions.md#death) in the 265 In particular, death tests don't like having multiple threads in the parent 274 leaving as few things as possible in it. Also, you can try to set the death test 277 If you go with thread-safe death tests, remember that they rerun the test 453 `ASSERT_DEATH(statement, matcher)` (or any death assertion macro) can be used [all …]
|
H A D | advanced.md | 420 (except by throwing an exception) in an expected fashion is also a death test. 422 Note that if a piece of code throws an exception, we don't consider it "death" 423 for the purpose of death tests, as the caller of the code could catch the 432 GoogleTest provides assertion macros to support death tests. See 433 [Death Assertions](reference/assertions.md#death) in the Assertions Reference 436 To write a death test, simply use one of the macros inside your test function. 441 // This death test uses a compound statement. 468 Note that a death test only cares about three things: 477 will **not** cause the death test to fail, as GoogleTest assertions don't abort 484 **test suite** (not test) `*DeathTest` when it contains a death test, as [all …]
|
H A D | primer.md | 377 > [death tests](advanced.md#death-tests)) and thus is not supported.
|
/freebsd/lib/googletest/gtest/ |
H A D | Makefile | 16 MAIN_INCS+= gtest/gtest-death-test.h 29 INTERNAL_INCS+= gtest/internal/gtest-death-test-internal.h
|
/freebsd/contrib/googletest/googletest/ |
H A D | CMakeLists.txt | 200 cxx_test(googletest-death-test-test gtest_main) 242 cxx_test_with_flags(gtest-death-test_ex_nocatch_test 244 gtest test/googletest-death-test_ex_test.cc) 245 cxx_test_with_flags(gtest-death-test_ex_catch_test 247 gtest test/googletest-death-test_ex_test.cc)
|
/freebsd/contrib/googletest/docs/reference/ |
H A D | assertions.md | 522 ## Death Assertions {#death} 525 terminate. For context, see [Death Tests](../advanced.md#death-tests). 534 * If the variable's value is `"fast"`, the death test statement is 538 extra flags to cause just the single death test under consideration to 541 re-executes the binary to cause just the single death test under 544 Other values for the variable are illegal and will cause the death test to fail. 548 If the death test statement runs to completion without dying, the child process 587 If death tests are supported, behaves the same as
|
/freebsd/lib/googletest/tests/gtest_main/ |
H A D | Makefile | 5 GTESTS+= googletest-death-test-test
|
/freebsd/share/misc/ |
H A D | flowers | 6 Bay leaf:I change but in death.
|
/freebsd/sbin/init/ |
H A D | init.c | 116 static state_func_t death(void); 1617 if (current_state == death) in get_current_state() 1680 requested_transition = death; in transition_handler() 1862 death(void) in death() function
|
H A D | NOTES | 110 7: death: send SIGHUP to all controlling processes, reap for 30 seconds,
|
/freebsd/contrib/atf/atf-sh/ |
H A D | libatf-sh.subr | 157 # Sets the expectations to 'death'. 163 Expect=death 686 death)
|
/freebsd/contrib/googletest/ |
H A D | BUILD.bazel | 157 # `gtest-death-test.cc` has `EXPECT_DEATH` that spawns a process,
|
H A D | README.md | 66 Googletest supports death tests, which verify that your code exits in a
|
/freebsd/share/dict/ |
H A D | web2a | 15873 death adder 15874 death agony 15875 death alder 15876 death angel 15877 death angle 15878 death-bearing 15881 death-begirt 15882 death bell 15883 death benefit 15884 death bill [all …]
|
/freebsd/usr.bin/m4/TEST/ |
H A D | test.m4 | 182 determine that the injury or death occurred due to the traveler's
|
/freebsd/contrib/one-true-awk/testdir/ |
H A D | bib | 530 …m a good way off, as it were a bow shot: for she said, Let me not see the death of the child. And … 659 …bekah, and she became his wife; and he loved her: and Isaac was comforted after his mother's death. 670 And it came to pass after the death of Abraham, that God blessed his son Isaac; and Isaac dwelt by … 704 …charged all his people, saying, He that toucheth this man or his wife shall surely be put to death. 711 …ays of Abraham his father; for the Philistines had stopped them after the death of Abraham: and he… 730 And he said, Behold now, I am old, I know not the day of my death: 735 … venison, and make me savoury meat, that I may eat, and bless thee before the LORD before my death. 738 And thou shalt bring it to thy father, that he may eat, and that he may bless thee before his death. 1795 …y sin only this once, and intreat the LORD your God, that he may take away from me this death only. 2039 …to the mount, or touch the border of it: whosoever toucheth the mount shall be surely put to death: [all …]
|
/freebsd/contrib/kyua/integration/ |
H A D | cmd_test_test.sh | 166 expect_all_pass:die -> expected_failure: This is the reason for death [S.UUUs]
|
/freebsd/contrib/ntp/ntpq/ |
H A D | ntpq.texi | 489 The original purpose was for kiss-o'-death (KoD) packets sent
|
H A D | ntpq-opts.def | 800 The original purpose was for kiss-o'-death (KoD) packets
|
/freebsd/contrib/ntp/ntpd/ |
H A D | invoke-ntp.conf.texi | 1402 for this purpose called the "kiss-of-death" (KoD) packet. 1444 and a kiss-o'-death packet returned if enabled. 1516 If this flag is set when a rate violation occurs, a kiss-o'-death
|
H A D | ntp.conf.def | 1469 for this purpose called the "kiss-of-death" (KoD) packet. 1515 and a kiss-o'-death packet returned if enabled. 1592 If this flag is set when a rate violation occurs, a kiss-o'-death
|