This is an automated email from the ASF dual-hosted git repository.

bugraoz pushed a change to branch make-airflow-integration-test-flaky
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard d9bac9334bd Mark airflowctl commands test as flaky with retries and 
change shadow naming in parametrize
 discard 0db4f3fd7d0 Mark airflowctl commands test as flaky with retries and 
change shadow naming in parametrize
     add d37e7d03938 Add workers.celery.livenessProbe section (#60186)
     add b63f014d6d9 Mark airflowctl commands test as flaky with retries and 
change shadow naming in parametrize
     add dde5fd1a158 Mark airflowctl commands test as flaky with retries and 
change shadow naming in parametrize

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (d9bac9334bd)
            \
             N -- N -- N   refs/heads/make-airflow-integration-test-flaky 
(dde5fd1a158)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 chart/newsfragments/60186.significant.rst          |  3 +
 chart/templates/NOTES.txt                          | 48 ++++++++++++
 chart/templates/workers/worker-deployment.yaml     | 14 ++--
 chart/values.schema.json                           | 56 ++++++++++++--
 chart/values.yaml                                  | 17 +++++
 .../tests/helm_tests/airflow_core/test_worker.py   | 85 ++++++++++++++++++++--
 6 files changed, 203 insertions(+), 20 deletions(-)
 create mode 100644 chart/newsfragments/60186.significant.rst

Reply via email to