jason810496 opened a new pull request, #56811:
URL: https://github.com/apache/airflow/pull/56811

   
   related: #56191
   
   The `test_remote_logging` e2e test is flaky because some of the logs are not 
yet uploaded to S3 before we validating log file names.
   
   Example fail run: 
https://github.com/apache/airflow/actions/runs/18613327530/job/53075269841?pr=55962
   ```
   =========================== short test summary info 
============================
   FAILED 
tests/airflow_e2e_tests/remote_log_tests/test_remote_logging.py::TestRemoteLogging::test_remote_logging_s3
 - AssertionError: None of the log sources 
['/opt/airflow/logs/dag_id=example_xcom_test/run_id=manual__2025-10-18T09:13:28.389807+00:00/task_id=bash_pull/attempt=1.log']
 were found in S3 bucket logs 
['s3://test-airflow-logs/dag_id=example_xcom_test/run_id=manual__2025-10-18T09:13:28.389807+00:00/task_id=bash_push/attempt=1.log',
 
's3://test-airflow-logs/dag_id=example_xcom_test/run_id=manual__2025-10-18T09:13:28.389807+00:00/task_id=pull_value_from_bash_push/attempt=1.log',
 
's3://test-airflow-logs/dag_id=example_xcom_test/run_id=manual__2025-10-18T09:13:28.389807+00:00/task_id=puller/attempt=1.log',
 
's3://test-airflow-logs/dag_id=example_xcom_test/run_id=manual__2025-10-18T09:13:28.389807+00:00/task_id=push/attempt=1.log',
 
's3://test-airflow-logs/dag_id=example_xcom_test/run_id=manual__2025-10-18T09:13:28.389807+00:00/task_id=push_by_returning/attempt=1.log']
   assert False
    +  where False = any(<generator object 
TestRemoteLogging.test_remote_logging_s3.<locals>.<genexpr> at 0x7f6276c88dd0>)
   =================== 1 failed, 1 passed, 1 warning in 46.40s 
====================
   ```
   
   ## What
   
   Add a retry mechanism to verify that a minimum number of TaskInstance logs 
are present in S3 before proceeding with validation.


-- 
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