baolsen edited a comment on pull request #16904:
URL: https://github.com/apache/airflow/pull/16904#issuecomment-890727738


   Great. I've rebased & pushed. Comparison below.
   
   Edit: 
   I wanted to compare the previous run to the current run, but both the runs 
now redirect to the same run. I realised that when I looked at the previous run 
and it had a redis-related failure, but now I can't find it. I'm not sure where 
to view the previous run for comparison. I've listed the failures in the run 
anyway in case we want to redo the CI (again), then we can compare.
   From what I can see the below failures are unrelated to my changes.
   
   **Previous run:**
   https://github.com/apache/airflow/pull/16904/checks?check_run_id=3208579465
   
   **Current run:**
   https://github.com/apache/airflow/pull/16904/checks?check_run_id=3217819682
   
   Postgres9.6,Py3.8: Always API Core Other CLI Providers WWW Integration
   Failures: CORE tests/jobs/test_scheduler_job.py
   
   Postgres13,Py3.9: Always API Core Other CLI Providers WWW Integration
   Failures: CORE tests/jobs/test_scheduler_job.py
   
   MySQL5.7, Py3.6: Always API Core Other CLI Providers WWW Integration
   Failures: Error: Process completed with exit code 137. **??**
   
   MySQL8, Py3.8: Always API Core Other CLI Providers WWW Integration
   Failures: INTEGRATION : TLS timeout
   
   MSSQL2019-latest, Py3.7: Always API Core Other CLI Providers WWW Integration
   Failures: CORE : tests/jobs/test_scheduler_job.py
   
   Sqlite Py3.6: Always API Core Other CLI Providers WWW Integration
   Failures: INTEGRATION: No failure log **??**
   
   Sqlite Py3.9: Always API Core Other CLI Providers WWW Integration
   Failures : TLS timeout
   
   Helm Chart; KubernetesExecutor (pull_request)
   Failures: No failure log **??**
   
   Helm Chart; CeleryExecutor (pull_request)
   Failures: No failure log **??**
   


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