Searched +full:python +full:- +full:tests (Results 1 – 25 of 1158) sorted by relevance
12345678910>>...47
| /external/tensorflow/tensorflow/compiler/tests/ |
| D | BUILD | 3 load("//tensorflow:tensorflow.bzl", "tf_cuda_cc_test") # buildifier: disable=same-origin-load
6 "//tensorflow/compiler/tests:build_defs.bzl",
14 load("//tensorflow/python/tpu:tpu.bzl", "tpu_py_test")
35 "//platforms/xla/tests/neural_nets",
49 "//tensorflow/python:array_ops",
50 "//tensorflow/python:client",
51 "//tensorflow/python:client_testlib",
52 "//tensorflow/python:framework",
53 "//tensorflow/python:platform",
54 "//tensorflow/python:random_seed",
[all …]
|
| /external/tensorflow/tensorflow/tools/dockerfiles/ |
| D | spec.yml | 8 # http://www.apache.org/licenses/LICENSE-2.0
33 - "{nightly}{jupyter}"
34 - "{_TAG_PREFIX}{ubuntu-devel}"
35 # Built per-release and pushed to tensorflow/tensorflow
36 # --arg _TAG_PREFIX=<val> should be set to "1.11" (for example) or "latest".
39 - "{_TAG_PREFIX}{ubuntu}{jupyter}"
42 - "{_TAG_PREFIX}{devel-onednn}"
43 - "{_TAG_PREFIX}{devel-onednn-mpich-horovod}"
44 - "{_TAG_PREFIX}{devel-onednn-mpich-horovod}{onednn-jupyter}"
45 - "{_TAG_PREFIX}{devel-onednn-mpi-horovod}"
[all …]
|
| /external/python/pyfakefs/.github/workflows/ |
| D | testsuite.yml | 8 runs-on: ubuntu-latest
10 - name: Check out repository
12 - name: Set up Python
13 uses: actions/setup-python@v4
15 python-version: "3.10"
16 - name: install pytype
18 - name: Run pytype
20 pytype pyfakefs --keep-going --exclude pyfakefs/tests/* --exclude pyfakefs/pytest_tests/*
22 tests:
23 runs-on: ${{ matrix.os }}
[all …]
|
| /external/libxml2/xstc/ |
| D | Makefile.am | 2 # Definition for the tests from W3C
4 PYSCRIPTS=nist-test.py ms-test.py sun-test.py
5 TESTDIR=Tests
7 TARBALL=xsts-2002-01-16.tar.gz
8 TARBALL_2=xsts-2004-01-14.tar.gz
9 TSNAME=xmlschema2002-01-16
10 TSNAME_2=xmlschema2004-01-14
11 TARBALLURL=http://www.w3.org/XML/2004/xml-schema-test-suite/$(TSNAME)/$(TARBALL)
12 TARBALLURL_2=http://www.w3.org/XML/2004/xml-schema-test-suite/$(TSNAME_2)/$(TARBALL_2)
13 MSTESTDEF=MSXMLSchema1-0-20020116.testSet
[all …]
|
| /external/python/cpython2/Lib/idlelib/idle_test/ |
| D | README.txt | 1 README FOR IDLE TESTS IN IDLELIB.IDLE_TEST
5 Automated unit tests were added in 2.7 for Python 2.x and 3.3 for Python 3.x.
6 To run the tests from a command line:
8 python -m test.test_idle
10 Human-mediated tests were added later in 2.7 and in 3.4.
12 python -m idlelib.idle_test.htest
43 2. GUI Tests
45 When run as part of the Python test suite, Idle GUI tests need to run
50 tests must be 'guarded' by "requires('gui')" in a setUp function or method.
53 To avoid interfering with other GUI tests, all GUI objects must be destroyed and
[all …]
|
| /external/protobuf/ |
| D | Makefile.am | 3 ACLOCAL_AMFLAGS = -I m4
7 # Build . before src so that our all-local and clean-local hooks kicks in at
17 # Build gmock before we build protobuf tests. We don't add gmock to SUBDIRS
18 # because then "make check" would also build and run all of gmock's own tests,
22 check-local:
28 # be careful because clean-local is also invoked during "make distclean", but
33 clean-local:
34 @if test -e third_party/googletest/Makefile; then \
38 if test -e conformance/Makefile; then \
42 if test -e benchmarks/Makefile; then \
[all …]
|
| /external/capstone/bindings/ |
| D | Makefile | 3 DIFF = diff -u -w
17 PYTHON2 ?= python
19 .PHONY: all expected python java ocaml
22 cd python && $(MAKE) gen_const
26 tests: expected python java #oclma ruby target
29 test_python: expected python
32 cd ../tests && $(MAKE)
33 mkdir -p $(TMPDIR)
34 ../tests/test > $(TEST)_e
35 ../tests/test_arm > $(TEST_ARM)_e
[all …]
|
| /external/curl/tests/ |
| D | README.md | 1 <!--
4 SPDX-License-Identifier: curl
5 -->
17 To run a specific set of tests (e.g. 303 and 410):
21 To run the tests faster, pass the -j (parallelism) flag:
23 make test TFLAGS="-j10"
26 perl script to run all the tests. The value of `TFLAGS` is passed
29 When you run tests via make, the flags `-a` and `-s` are passed, meaning
30 to continue running tests even after one fails, and to emit short output.
33 You must `chdir` into the tests directory, then you can run it like so:
[all …]
|
| /external/cronet/third_party/protobuf/ |
| D | Makefile.am | 3 ACLOCAL_AMFLAGS = -I m4
7 # Build . before src so that our all-local and clean-local hooks kicks in at
14 # Build gmock before we build protobuf tests. We don't add gmock to SUBDIRS
15 # because then "make check" would also build and run all of gmock's own tests,
19 check-local:
25 # be careful because clean-local is also invoked during "make distclean", but
30 clean-local:
31 @if test -e third_party/googletest/Makefile; then \
35 if test -e conformance/Makefile; then \
39 if test -e benchmarks/Makefile; then \
[all …]
|
| /external/python/cpython3/Lib/idlelib/idle_test/ |
| D | README.txt | 1 README FOR IDLE TESTS IN IDLELIB.IDLE_TEST
5 Automated unit tests were added in 3.3 for Python 3.x.
6 To run the tests from a command line:
8 python -m test.test_idle
10 Human-mediated tests were added later in 3.4.
12 python -m idlelib.idle_test.htest
27 contains code needed or possibly needed for gui tests. See the next
28 section if doing gui tests. If not, and not needed for further classes,
42 2. GUI Tests
44 When run as part of the Python test suite, Idle GUI tests need to run
[all …]
|
| /external/grpc-grpc/summerofcode/2018/ |
| D | naresh.md | 5 Enable Building of gRPC Python with Bazel
9 gRPC Python currently has a constellation of scripts written to build the
11 [Bazel](https://bazel.build/) is the open-sourced variant of Google's internal
14 development, especially in terms of Python (amongst a few other languages).
16 The project aimed to fill this gap and build gRPC Python with Bazel.
20 …storage.googleapis.com/summerofcode-prod.appspot.com/gsoc/core_project/doc/5316764725411840_152204…
24 ### State of Bazel for Python
28 rules for Python are currently being separated out into their own repo at
32 Python](https://groups.google.com/forum/#!topic/bazel-sig-python/iQjV9sfSufw)
33 though. There's still challenges when it comes to building for Python 2 vs 3.
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/summerofcode/2018/ |
| D | naresh.md | 5 Enable Building of gRPC Python with Bazel
9 gRPC Python currently has a constellation of scripts written to build the
11 [Bazel](https://bazel.build/) is the open-sourced variant of Google's internal
14 development, especially in terms of Python (amongst a few other languages).
16 The project aimed to fill this gap and build gRPC Python with Bazel.
20 …storage.googleapis.com/summerofcode-prod.appspot.com/gsoc/core_project/doc/5316764725411840_152204…
24 ### State of Bazel for Python
28 rules for Python are currently being separated out into their own repo at
32 Python](https://groups.google.com/forum/#!topic/bazel-sig-python/iQjV9sfSufw)
33 though. There's still challenges when it comes to building for Python 2 vs 3.
[all …]
|
| /external/python/google-api-python-client/ |
| D | CONTRIBUTING.rst | 11 …/kubernetes/community/blob/master/contributors/guide/pull-requests.md#best-practices-for-faster-re…
21 - The feature must be documented in both the API and narrative
24 - The feature must work fully on the following CPython versions:
27 - The feature must not add unnecessary dependencies (where
37 - While logged into your GitHub account, navigate to the
38 ``google-api-python-client`` `repo`_ on GitHub.
40 - Fork and clone the ``google-api-python-client`` repository to your GitHub account by
43 - Clone your fork of ``google-api-python-client`` from your GitHub account to your local
45 as ``hack-on-google-api-python-client``. E.g.::
48 $ git clone git@github.com:USERNAME/google-api-python-client.git hack-on-google-api-python-client
[all …]
|
| /external/scapy/.travis/ |
| D | test.sh | 3 python -c 'import sys; print("sys.path:" , sys.path)'
6 …python -c 'import '$DEPENDENCY'; print("'$DEPENDENCY': "+str(getattr('$DEPENDENCY', "__version__",…
7 echo "----"
15 python --version
16 python -c "from scapy.all import *; print(conf)"
18 # Don't run tests that require root privileges
19 if [ -z "$SCAPY_SUDO" -o "$SCAPY_SUDO" = "false" ]
21 UT_FLAGS="-K netaccess -K needs_root -K manufdb"
24 SCAPY_SUDO="$SCAPY_SUDO -H"
29 UT_FLAGS+=" -K not_pcapdnet"
[all …]
|
| /external/scapy/ |
| D | .appveyor.yml | 3 # Python versions that will be tested
6 - PYTHON: "C:\\Python27-x64"
9 - PYTHON: "C:\\Python36-x64"
18 - ps: .\.appveyor\InstallNpcap.ps1
19 - ps: .\.appveyor\InstallWindump.ps1
20 - choco install -y wireshark
21 # Install Python modules
22 - "%PYTHON%\\python -m pip install cryptography coverage mock"
23 - set PATH="%PYTHON%\\Scripts\\;%PATH%"
27 - set PYTHONPATH=%APPVEYOR_BUILD_FOLDER%
[all …]
|
| /external/python/google-auth-library-python/ |
| D | noxfile.py | 7 # http://www.apache.org/licenses/LICENSE-2.0
26 "tests",
34 @nox.session(python="3.7")
36 session.install("flake8", "flake8-import-order", "docutils", BLACK_VERSION)
37 session.install("-e", ".")
38 session.run("black", "--check", *BLACK_PATHS)
41 "--import-order-style=google",
42 "--application-import-names=google,tests,system_tests",
44 "tests",
48 "python", "setup.py", "check", "--metadata", "--restructuredtext", "--strict"
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/third_party/upb/.github/workflows/ |
| D | python_tests.yml | 1 name: Python Tests
6 - main
7 - '[0-9]+.x'
10 - main
11 - '[0-9]+.x'
17 runs-on: ubuntu-large
21 …DOCKER_IMAGE: us-docker.pkg.dev/protobuf-build/release-containers/linux/apple@sha256:bb1d147384499…
24 - uses: actions/checkout@v2
25 - name: Set up Cloud SDK
26 uses: google-github-actions/auth@v0
[all …]
|
| /external/python/cpython2/Doc/library/ |
| D | test.rst | 2 :mod:`test` --- Regression tests package for Python
6 :synopsis: Regression tests package containing the testing suite for Python.
7 .. sectionauthor:: Brett Cannon <brett@python.org>
10 The :mod:`test` package is meant for internal use by Python only. It is
11 documented for the benefit of the core developers of Python. Any use of
12 this package outside of Python's standard library is discouraged as code
14 Python.
17 The :mod:`test` package contains all regression tests for Python as well as the
19 :mod:`test.support` is used to enhance your tests while
23 testing suite for a specific module or feature. All new tests should be written
[all …]
|
| /external/pigweed/pw_build/ |
| D | python.rst | 1 .. _module-pw_build-python:
4 Python GN Templates
6 .. pigweed-module-subpage::
9 The Python build is implemented with GN templates defined in
10 ``pw_build/python.gni``. See the .gni file for complete usage documentation.
14 - :bdg-ref-primary-line:`docs-python-build` for an overview on how Python in
16 - The :bdg-ref-primary-line:`module-pw_build` docs for other GN templates
19 .. _module-pw_build-python-base-templates:
21 ---------------------
22 Python Base Templates
[all …]
|
| D | python.gni | 7 # https://www.apache.org/licenses/LICENSE-2.0
24 # Constraints file selection (arguments to pip install --constraint).
32 # If true, GN will run each Python test using the coverage command. A separate
34 # this information run: pw presubmit --step gn_python_test_coverage
42 # For example: if lib_a depends on lib_b, lib_a.tests will run after first
43 # running lib_b.tests if pw_build_TEST_TRANSITIVE_PYTHON_DEPS is true.
45 # If pw_build_TEST_TRANSITIVE_PYTHON_DEPS is false, tests for a
47 # lib_b.tests) OR if the pw_python_package is placed in a pw_python_group AND
48 # you build the group.tests target.
50 # This applies to mypy, pylint, and tests.
[all …]
|
| /external/python/python-api-core/ |
| D | CONTRIBUTING.rst | 10 …/kubernetes/community/blob/master/contributors/guide/pull-requests.md#best-practices-for-faster-re…
20 - The feature must be documented in both the API and narrative
23 - The feature must work fully on the following CPython versions:
26 - The feature must not add unnecessary dependencies (where
36 - While logged into your GitHub account, navigate to the
37 ``python-api-core`` `repo`_ on GitHub.
39 - Fork and clone the ``python-api-core`` repository to your GitHub account by
42 - Clone your fork of ``python-api-core`` from your GitHub account to your local
44 as ``hack-on-python-api-core``. E.g.::
47 $ git clone git@github.com:USERNAME/python-api-core.git hack-on-python-api-core
[all …]
|
| /external/rappor/ |
| D | README.md | 7 This repository contains simulation and analysis code in Python and R.
13 [rappor-discuss@googlegroups.com][group].
16 ----------------
18 Although the Python and R libraries should be portable to any platform, our
19 end-to-end demo has only been tested on Linux.
28 This compiles and tests the `fastrand` C extension module for Python, which
34 The demo strings together the Python and R code. It:
37 2. Runs it through the RAPPOR privacy-preserving reporting mechanisms
44 ------------
46 [R](http://r-project.org) analysis (`analysis/R`):
[all …]
|
| /external/python/cpython3/Modules/_decimal/tests/ |
| D | runall-memorydebugger.sh | 7 # Synopsis: ./runall-memorydebugger.sh [--all-configs64 | --all-configs32]
18 CONFIGS_32="ppro ansi32 ansi-legacy universal"
20 VALGRIND="valgrind --tool=memcheck --leak-resolution=high \
21 --suppressions=Misc/valgrind-python.supp"
25 *--all-configs64*)
28 *--all-configs32*)
45 len=`echo $@ | wc -c`
46 margin="#%"`expr \( 74 - $len \) / 2`"s"
59 # test_decimal: refleak, regular and Valgrind tests
60 for args in "--without-decimal-contextvar" ""; do
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/tools/run_tests/ |
| D | README.md | 3 This directory contains scripts that facilitate building and running tests. We are using python scr…
4 tests because that gives us the opportunity to run tests using the same commandline regardless of t…
6 # Unit tests (run_tests.py)
8 Builds gRPC in given language and runs unit tests. Use `tools/run_tests/run_tests.py --help` for mo…
11 `tools/run_tests/run_tests.py -l python -c dbg`
14 - `--use_docker` Builds a docker container containing all the prerequisites for given language and …
15 - `--build_only` Only build, do not run the tests.
17 …as `ImportError: No module named httplib2`, then you may be missing some Python modules. Install t…
19 Note: some tests may be flaky. Check the "Issues" tab for known flakes and other issues.
21 The full suite of unit tests will take many minutes to run.
[all …]
|
| /external/grpc-grpc/tools/run_tests/ |
| D | README.md | 3 This directory contains scripts that facilitate building and running tests. We are using python scr…
4 tests because that gives us the opportunity to run tests using the same commandline regardless of t…
6 # Unit tests (run_tests.py)
8 Builds gRPC in given language and runs unit tests. Use `tools/run_tests/run_tests.py --help` for mo…
11 `tools/run_tests/run_tests.py -l python -c dbg`
14 - `--use_docker` Builds a docker container containing all the prerequisites for given language and …
15 - `--build_only` Only build, do not run the tests.
17 …as `ImportError: No module named httplib2`, then you may be missing some Python modules. Install t…
19 Note: some tests may be flaky. Check the "Issues" tab for known flakes and other issues.
21 The full suite of unit tests will take many minutes to run.
[all …]
|
12345678910>>...47