Home
last modified time | relevance | path

Searched refs:search (Results 1 – 6 of 6) sorted by relevance

/honee/tests/
H A Djunit.py213 search=args.search,
H A Djunit_common.py769 …suite_spec: SuiteSpec, pool_size: int = 1, search: str = ".*", verbose: bool = False) -> TestSuite:
786 …t for t in get_test_args(suite_spec.get_source_path(test)) if re.search(search, t.name, re.IGNOREC…
/honee/
H A Dindex.md24 - {ref}`search`
H A DMakefile323 …as-torch $(USE_TORCH) )--nproc $(NPROC_TEST) --pool-size $(NPROC_POOL) --search '$(subsearch)' $(<…
330 search ?= navierstokes macro
332 realsearch = $(search:%=%%)
345 …),--has-torch $(USE_TORCH) )--nproc $(NPROC_TEST) --pool-size $(NPROC_POOL) --search '$(subsearch)'
354 …as-torch $(USE_TORCH) )--nproc $(NPROC_TEST) --pool-size $(NPROC_POOL) --search '$(subsearch)' $(<…
H A Dpytorch_pkgconfig.py43 regex_result = regex_ABI.search(line)
H A DDoxyfile826 # search path. See also \cite for info how to create references.
1232 # tools must be available from the command line (i.e. in the search path).
1511 # HTML files also contain an index, a table of contents, and you can search for
1828 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1829 # the HTML output. The underlying search engine uses javascript and DHTML and
1832 # there is already a search function so this one should typically be disabled.
1833 # For large projects the javascript based search engine can be slow, then
1835 # search using the keyboard; to jump to the search box use <access key> + S
1837 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1838 # key> to jump into the search results window, the results can be navigated
[all …]