The GitHub Actions job "Tests" on airflow.git has failed. Run started by GitHub user dstandish (triggered by dstandish).
Head commit for run: 6d6ac2b2bcbb0547a488a1a13fea3cb1a69d24e8 / Daniel Standish <[email protected]> Purge duplicates from TaskFail prior to 2.3 upgrade (#22769) We're adding a PK to TaskFail in 2.3 so we wanted to check and move dupes out of the table prior to upgrade. Why do we do it in pre-upgrade check instead of in the migration? (1) historical reasons, we initially only "checked" and failed with this type of thing but then realized we needed to actualy move the rows out but did want to move the code (2) will take a little more thought concering how to implement with `--sql-mode` given that we don't know until we run the migrations whether those `_airflow_moved` tables will need to be created and if we create them unnecessarily then many users will get unneeded warnings in the web UI (we warn and tell users to deal with these tables if they are created). Report URL: https://github.com/apache/airflow/actions/runs/2168455792 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
