This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new ab72e944dba Replacee `breeze testing tests` command in a few places
remaining (#44299)
ab72e944dba is described below
commit ab72e944dbae075b867db9e175bff12dbf106ff2
Author: Jarek Potiuk <[email protected]>
AuthorDate: Sat Nov 23 23:29:59 2024 +0000
Replacee `breeze testing tests` command in a few places remaining (#44299)
Follow up after #43979 to remove a few remaining places where
old `breeze testing tests` command was used.
---
Dockerfile.ci | 2 +-
contributing-docs/05_pull_requests.rst | 3 ++-
dev/breeze/doc/03_developer_tasks.rst | 2 +-
dev/breeze/doc/05_test_commands.rst | 8 ++++----
scripts/docker/entrypoint_ci.sh | 2 +-
5 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/Dockerfile.ci b/Dockerfile.ci
index 05233f06419..8fb36054eed 100644
--- a/Dockerfile.ci
+++ b/Dockerfile.ci
@@ -1080,7 +1080,7 @@ function check_run_tests() {
if [[ ${REMOVE_ARM_PACKAGES:="false"} == "true" ]]; then
# Test what happens if we do not have ARM packages installed.
# This is useful to see if pytest collection works without ARM
packages which is important
- # for the MacOS M1 users running tests in their ARM machines with
`breeze testing tests` command
+ # for the MacOS M1 users running tests in their ARM machines with
`breeze testing *-tests` command
python "${IN_CONTAINER_DIR}/remove_arm_packages.py"
fi
diff --git a/contributing-docs/05_pull_requests.rst
b/contributing-docs/05_pull_requests.rst
index 1e141679434..db25643d74b 100644
--- a/contributing-docs/05_pull_requests.rst
+++ b/contributing-docs/05_pull_requests.rst
@@ -88,7 +88,8 @@ these guidelines:
to the changed code (for example for ``airflow/cli/cli_parser.py`` changes
you have tests in
``tests/cli/test_cli_parser.py``). However there are a number of cases
where the tests that should run
are placed elsewhere - you can either run tests for the whole
``TEST_TYPE`` that is relevant (see
- ``breeze testing tests --help`` output for available test types) or you
can run all tests, or eventually
+ ``breeze testing core-tests --help`` or ``breeze testing providers-tests
--help`` output for
+ available test types for each of the testing commands) or you can run all
tests, or eventually
you can push your code to PR and see results of the tests in the CI.
- You can use any supported python version to run the tests, but the best is
to check
diff --git a/dev/breeze/doc/03_developer_tasks.rst
b/dev/breeze/doc/03_developer_tasks.rst
index 87bb2713b93..ad1a4fe0a6f 100644
--- a/dev/breeze/doc/03_developer_tasks.rst
+++ b/dev/breeze/doc/03_developer_tasks.rst
@@ -419,7 +419,7 @@ are several reasons why you might want to do that.
Breeze uses docker images heavily and those images are rebuild periodically
and might leave dangling, unused
images in docker cache. This might cause extra disk usage. Also running
various docker compose commands
-(for example running tests with ``breeze testing tests``) might create
additional docker networks that might
+(for example running tests with ``breeze testing core-tests``) might create
additional docker networks that might
prevent new networks from being created. Those networks are not removed
automatically by docker-compose.
Also Breeze uses it's own cache to keep information about all images.
diff --git a/dev/breeze/doc/05_test_commands.rst
b/dev/breeze/doc/05_test_commands.rst
index 3ce2f366db9..f5b3a78eef7 100644
--- a/dev/breeze/doc/05_test_commands.rst
+++ b/dev/breeze/doc/05_test_commands.rst
@@ -106,9 +106,9 @@ For example this will run API and WWW tests in parallel:
.. code-block:: bash
- breeze testing tests --parallel-test-types "API WWW" --run-in-parallel
+ breeze testing core-tests --parallel-test-types "API WWW" --run-in-parallel
-Here is the detailed set of options for the ``breeze testing tests`` command.
+Here is the detailed set of options for the ``breeze testing core-tests``
command.
.. image:: ./images/output_testing_core-tests.svg
:target:
https://raw.githubusercontent.com/apache/airflow/main/dev/breeze/images/output_testing_core-tests.svg
@@ -143,11 +143,11 @@ You can also run parallel tests with
``--run-in-parallel`` flag - by default it
in parallel, but you can specify the test type that you want to run with space
separated list of test
types passed to ``--parallel-test-types`` flag.
-For example this will run API and WWW tests in parallel:
+For example this will run ``amazon`` and ``google`` tests in parallel:
.. code-block:: bash
- breeze testing tests --parallel-test-types "Providers[amazon]
Providers[google]" --run-in-parallel
+ breeze testing providers-tests --parallel-test-types "Providers[amazon]
Providers[google]" --run-in-parallel
Here is the detailed set of options for the ``breeze testing providers-test``
command.
diff --git a/scripts/docker/entrypoint_ci.sh b/scripts/docker/entrypoint_ci.sh
index 5ff608adeab..956b18a666b 100755
--- a/scripts/docker/entrypoint_ci.sh
+++ b/scripts/docker/entrypoint_ci.sh
@@ -316,7 +316,7 @@ function check_run_tests() {
if [[ ${REMOVE_ARM_PACKAGES:="false"} == "true" ]]; then
# Test what happens if we do not have ARM packages installed.
# This is useful to see if pytest collection works without ARM
packages which is important
- # for the MacOS M1 users running tests in their ARM machines with
`breeze testing tests` command
+ # for the MacOS M1 users running tests in their ARM machines with
`breeze testing *-tests` command
python "${IN_CONTAINER_DIR}/remove_arm_packages.py"
fi
