Home
last modified time | relevance | path

Searched full:scenario (Results 1 – 25 of 641) sorted by relevance

12345678910>>...26

/freebsd/tools/regression/security/proc_to_proc/
H A Dscenario.c52 * Description of a scenario.
54 struct scenario { struct
89 static const struct scenario scenarios[] = {
137 int scenarios_count = sizeof(scenarios) / sizeof(struct scenario);
260 * Enact a scenario by looping through the four test cases for the scenario,
265 enact_scenario(int scenario) in enact_scenario() argument
281 error = cred_set(scenarios[scenario].sc_cred2); in enact_scenario()
314 error = cred_set(scenarios[scenario].sc_cred1); in enact_scenario()
326 * by extracting it from the scenario table. in enact_scenario()
337 scenarios[scenario].sc_canptrace_errno; in enact_scenario()
[all …]
/freebsd/contrib/kyua/engine/
H A Dtap_helpers.cpp66 /// A test scenario that validates the TEST_ENV_* variables.
92 /// A test scenario that crashes.
100 /// A test scenario that reports some tests as failed.
113 /// A test scenario that passes.
126 /// A test scenario that passes but then exits with non-zero.
137 /// A test scenario that times out.
161 /// The caller can select which test scenario to run by modifying the program's
165 /// one for every "test scenario". We use this program as a dispatcher for
177 std::cerr << "No arguments allowed; select the test scenario with the " in main()
197 std::cerr << "Unknown test scenario\n"; in main()
/freebsd/sys/contrib/device-tree/Bindings/
H A Dcommon-properties.txt33 Scenario 1 : CPU in LE mode & device in LE mode.
41 Scenario 2 : CPU in LE mode & device in BE mode.
49 Scenario 3 : CPU in BE mode & device in BE mode.
57 Scenario 4 : CPU in BE mode & device in LE mode.
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/snapshot/
H A Dsnapshot_016_pos.ksh64 # scenario 1
73 # scenario 2
82 # promote back to $TESTPOOL/$TESTFS for scenario 3
87 # scenario 3
/freebsd/tests/sys/cddl/zfs/tests/snapshot/
H A Dsnapshot_016_pos.ksh79 # scenario 1
88 # scenario 2
97 # promote back to $TESTPOOL/$TESTFS for scenario 3
102 # scenario 3
/freebsd/sys/contrib/dev/iwlwifi/fw/api/
H A Dsf.h19 /* Smart Fifo possible scenario */
71 * @long_delay_timeouts: aging and idle timer values for each scenario
73 * @full_on_timeouts: timer values for each scenario in full on state.
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/block_cloning/
H A Dblock_cloning_clone_mmap_write.ksh29 # and write from the map into the file. PR#15656 fixes this scenario.
30 # This scenario also causes data corruption on FreeBSD, which is fixed
58 log_assert "Test for clone, mmap and write scenario"
/freebsd/sys/tools/syscalls/examples/cpp/
H A Dsyscalls.master7 ; Scenario #1: Vendor uses a reserved slot on just a single platform
18 ; Scenario #2: The other way around; vendor obsoletes a syscall on newer
/freebsd/sys/contrib/device-tree/Bindings/leds/
H A Dleds-bcm6328.txt73 Scenario 1 : BCM6328 with 4 EPHY LEDs
114 Scenario 2 : BCM63268 with Serial/GPHY0 LEDs
195 Scenario 3 : BCM6362 with 1 LED for each EPHY
247 Scenario 4 : BCM6362 with 1 LED for all EPHYs
275 Scenario 5 : BCM6362 with EPHY LEDs swapped
H A Dleds-bcm6358.txt34 Scenario 1 : BCM6358
63 Scenario 2 : BCM6368
/freebsd/tools/test/stress2/misc/
H A Dsignal2.sh3 # Test scenario from:
5 # Test scenario by: Li-Wen Hsu <lwhsu@FreeBSD.org>
H A Dprocstat2.sh30 # This test scenario would trigger an NMI.
33 # Test scenario idea by Mark Johnston <markj@freebsd.org>
H A Dsuj24.sh29 # Scenario from kern/160662
30 # Scenario by Hans Ottevanger <hans beastielabs net>
H A Dnuma.sh30 # Test scenario: Last memory domain significantly smaller than the others.
32 # Test scenario description by markj@
H A Dnullfs6.sh30 # Test scenario by Mikolaj Golub <to my trociny gmail com>
46 cp $nullfs_srcdir/1/test.file $nullfs_srcdir/2/test.file # scenario by kib
H A Drename13.sh29 # Regression test for crossmp scenario:
34 # Test scenario by: fnacl@protonmail.com
H A Dshm3.sh3 # Test scenario for Bug 261707.
7 # Test scenario suggestion by kib@
H A Dsuj15.sh31 # mksnap_ffs(8) test scenario inspired by Christian Gusenbauer, c47g gmx at.
33 # Three problems seen with this scenario:
H A Dprocfs5.sh30 # Test scenario based on panic seen in
34 # Scenario by kib@
H A Dpty2.sh29 # pty(4) test scenario.
34 # Based on test scenario by Bruce Evans.
H A Dufssuspend.sh3 # ioctl(g_ufs_suspend_handle, UFSSUSPEND, &statfsp->f_fsid) test scenario.
7 # Test scenario by Dexuan Cui <decui microsoft com>
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zfs/
H A Dzfs_003_neg.ksh55 log_assert "zfs fails with unexpected scenario."
74 log_pass "zfs fails with unexpected scenario as expected."
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/pool_checkpoint/
H A Dcheckpoint_invalid.ksh55 # Scenario 1
70 # Scenario 2
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zpool_split/
H A Dzpool_split_resilver.ksh25 # The first scenario:
32 # The second scenario:
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/removal/
H A Dremoval_with_faulted.ksh39 # We want to setup a scenario where the default mapping would make
60 # 3. We fault two children to force the scenario described above.

12345678910>>...26