Searched full:cases (Results 1 – 25 of 4781) sorted by relevance
12345678910>>...192
meson-1.0.0/ meson-1.0.0/COPYING meson-1.0.0/ ...
34 def _validate_test_case_depends(cases, depends): argument36 if not case in cases:39 if not dep in cases:41 ", cases available %s." % (case, dep, str(cases.keys())))43 def _order_test_case_by_depends(cases, depends): argument49 raise OEQADependency("Test cases %s and %s have a circular" \55 dep_graph['__root__'] = cases.keys()56 for case in cases:66 return [cases[case_id] for case_id in cases_ordered]92 _validate_test_case_depends(registry['cases'], registry['depends'])[all …]
38 # OETestLoader call it when is loading test cases.42 # registry) of a cases that were filtered.60 # OETestLoader call it after discover test cases61 # needs to return the cases to be run.64 return registry['cases']
17 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi…18 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik…39 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi…40 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik…61 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi…62 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik…83 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi…84 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik…105 …Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wi…106 …ed_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wik…[all …]
59 cases. To disable execution within the namespace, pass the -N option77 future). A test suite has one or more test cases in it.106 executed as part of the test. More will be added as test cases require.111 The NAMES values are used to substitute into the commands in the test cases.131 Execute test cases that use a physical device, where137 select which test cases: files plus directories; filtered by categories150 Execute the specified test cases with specified IDs153 select action to perform on selected test cases155 -l, --list List all test cases, or those only within the157 -s, --show Display the selected test cases[all …]
68 Get all required plugins from the list of test cases and return86 Get all required plugins from the list of test cases and load any plugin431 Open the JSON file containing the test cases and return them468 'selection', 'select which test cases: ' +471 'action', 'select action to perform on selected test cases')486 help='Execute the specified test cases with specified IDs')489 help='List all test cases, or those only within the specified category')492 help='Display the selected test cases')495 help='Generate ID numbers for new test cases')504 help='Execute test cases that use a physical device, ' +[all …]
103 self.tc._registry['cases'][case_id] = case135 # 'auto' is a reserved key word to run test cases automatically217 Returns a suite of all tests cases contained in testCaseClass.220 raise TypeError("Test cases should not be derived from TestSuite." \258 for case in self.tc._registry['cases']:265 raise OEQATestNotFound("Not found %s in loaded test cases" % \276 cases = None280 cases = clss.discover(self.tc._registry)285 return self.suiteClass(cases) if cases else big_suite322 Returns a suite of all tests cases contained in module.[all …]
119 cases are run first thing at module load time. When the Bluetooth120 subsystem is compiled into the kernel image, then the test cases124 bool "ECDH test cases"127 Run test cases for ECDH cryptographic functionality used by the131 bool "SMP test cases"134 Run test cases for SMP cryptographic functionality, including both
7 diff --git a/cases/stress/hwpoison/Makefile b/cases/stress/hwpoison/Makefile9 --- a/cases/stress/hwpoison/Makefile10 +++ b/cases/stress/hwpoison/Makefile
24 # Merge gcov graph from several test cases. This can be used to check25 # the coverage of several test cases.70 # Merge mce serverity coverage file from several test cases. This can71 # be used to check the coverage of several test cases.
1 # test case management tool - manual execution from testopia test cases123 cases = load_json_file(case_file)133 for case in copy.deepcopy(cases) :135 cases.remove(case)137 print('\nTotal number of test cases in this test suite: %s\n' % len(cases))138 for c in cases:194 cases = load_json_file(case_file)200 for case in cases:235 … help='make the testcase configuration file to run a set of test cases based on user selection')
37 # NOTE: the 'in' and 'out' cases are usually bulk, but can be106 echo '** Control test cases:'124 echo '** Host Write (OUT) test cases:'155 echo '** Host ISOCHRONOUS Write (OUT) test cases:'182 echo '** Host Read (IN) test cases:'208 echo '** Host ISOCHRONOUS Read (IN) test cases:'
1 tdc - Adding test cases for tdc5 ADDING TEST CASES10 template.json for the required JSON format for test cases.18 If you wish to store your custom test cases elsewhere, be sure to run81 in the test cases. tdc will output a series of TAP results for the skipped
5 // There can be false positives in cases where the positional7 // is a placeholder for not yet handled cases.17 // the two known cases are:38 // All other cases look like bugs or at least lack of documentation
79 from the current review queue. Likewise for cases where patches would198 at the end of the week. In some cases pull requests could additionally217 Q: Verifier changes and test cases219 Q: I made a BPF verifier change, do I need to add test cases for223 it is absolutely necessary to add test cases to the BPF kernel228 cases, including a lot of corner cases that LLVM BPF back end may229 generate out of the restricted C code. Thus, adding test cases is231 affect prior use-cases. Thus, treat those test cases as: verifier244 The more test cases we add to BPF selftests, the better the coverage311 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is[all …]
44 the specific IOMMU. Below are a few examples of typical use-cases:51 In such cases the number of cells will usually be 1 as in the next case.53 in order to enable translation for a given master. In such cases the single54 address cell corresponds to the master device's ID. In some cases more than62 Note that these are merely examples and real-world use-cases may use different85 have a means to turn off translation. But it is invalid in such cases to
376 // handle degenerate cases of proto::or_391 // handle degenerate cases of proto::and_409 …template<typename Expr, typename Tag, typename Args, long Arity, typename Cases, typename Transfor…410 struct matches_<Expr, proto::basic_expr<Tag, Args, Arity>, switch_<Cases, Transform> >414 , typename Cases::template case_<420 typename Cases::template case_<427 template<typename Expr, typename Tag, typename Args, long Arity, typename Cases>428 struct matches_<Expr, proto::basic_expr<Tag, Args, Arity>, switch_<Cases> >432 , typename Cases::template case_<Tag>::proto_grammar435 typedef typename Cases::template case_<Tag> which;[all …]
23 // optional<T> vs optional<T> cases58 // optional<T> vs T cases91 // T vs optional<T> cases126 // optional<T> vs none cases160 // none vs optional<T> cases
312 Use cases386 Use cases437 Use cases483 Use cases544 Use cases593 Use cases638 Use cases673 Use cases720 Use cases770 Use cases[all …]
11 those unusual cases where percpu-ref would consume too much memory,82 update (write) stream. In such cases, atomic_inc_not_zero() might be84 use atomic_inc() in such cases.87 search_and_reference() code path. In such cases, the139 In cases where delete() can sleep, synchronize_rcu() can be called from
46 * Handle the cases when at least one of x, y or z is a NaN. in _sp_maddf()64 /* ZERO z cases are handled separately below */ in _sp_maddf()84 * Cases of addition of infinities with opposite signs in _sp_maddf()105 /* Handle cases +0 + (-0) and similar ones. */ in _sp_maddf()108 * Cases of addition of zeros of equal signs in _sp_maddf()
78 writes have occurred in the specific cases the author cares. This kind80 cases, the read used to flush the device may be expected to fail (if the109 complete. In many cases, however, the driver may want to indicate that the112 these cases, although only some platforms will honor the relaxed115 provides examples of how to use readX_relaxed(). In many cases, a majority
8 #define VERBOSE 0 /* Set to '1' for more logging of test cases */32 * The arguments given to test cases can be one of three types.85 * Building blocks for test cases.95 * Some specific test cases may make use of other custom constructs.198 * Macros to define test cases.200 * Those of the form TEST_{R,P,M}* can be used to define test cases439 /* Various values used in test cases... */
47 cases = set(getSuiteCasesIDs(tc.suites))48 msg = 'Expected just %s cases' % ', '.join(expected_cases)49 self.assertEqual(cases, expected_cases, msg=msg)
18 In some cases it may be necessary to describe non-probeable device20 such cases, child nodes for those devices will be present as28 Instance ID Is for the cases where multiple Devices of the