sidshas03 commented on PR #63355:
URL: https://github.com/apache/airflow/pull/63355#issuecomment-4137181711

   > I am OOO for next couple of days.
   > 
   > cc @amoghrajesh who can help get this along the finish line.
   
   Thanks for checking @kaxil @amoghrajesh. Just wanted to let you know that, I 
reviewed the latest CI run for this PR (`23602955532`) and confirmed the 
current failures are in unrelated jobs:
   
   1) CI image checks / MyPy checks (mypy-providers)
   - Failing file: 
`providers/cncf/kubernetes/src/airflow/providers/cncf/kubernetes/hooks/kubernetes.py`
 (line 1085)
   - Error: `Found 3 errors in 1 file (checked 4282 source files)`
   
   2) Integration and System Tests / Integration: providers elasticsearch
   - Failing tests:
     - 
`providers/elasticsearch/tests/integration/elasticsearch/log/test_es_remote_log_io.py::TestElasticsearchRemoteLogIOIntegration::test_upload_and_read`
     - `...::test_read_missing_log`
     - `...::test_read_error_detail_integration`
   - Error in all three: `elasticsearch.BadRequestError ... 
media_type_header_exception ... Accept=application/vnd.elasticsearch+json; 
compatible-with=9` (expects version 7 or 8)
   
   3) Additional PROD image tests / Elasticsearch remote logging e2e
   - Failing tests:
     - 
`tests/airflow_e2e_tests/remote_log_elasticsearch_tests/test_remote_logging_elasticsearch.py::TestRemoteLoggingElasticsearch::test_remote_logging_elasticsearch`
     - `...::test_remote_logging_elasticsearch_error_detail`
   - Same root error: `media_type_header_exception` with `compatible-with=9`
   
   My PR changes are scoped to:
   - 
`airflow-core/src/airflow/api_fastapi/execution_api/routes/task_instances.py`
   - 
`airflow-core/tests/unit/api_fastapi/execution_api/versions/head/test_task_instances.py`
   
   So these failures appear to be outside the scope of this PR.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to