potiuk commented on issue #19578: URL: https://github.com/apache/airflow/issues/19578#issuecomment-974682581
> So unless we change the semantic for `dags test` and `tasks test` (which is not trivial), Why don't we add "data-interval' to `dags test` and `tasks tests` command to specify it manually ? Those are tests commands for user to try things out, they could add data interval there and we could provide a helpful explanation and hint what data interval they should add if they don't specify them for Custom timetable. > The easiest solution would be to simply delete that run and re-trigger it on Airflow 2.2, or we could potentially provide a script for the user to “migrate” that existing run to 2.2. But I think in this case the run does not even exist - so we have nothing to delete. `airflow tasks test` I believe does not even look nor modify DagRun table - as I remember (and commented in #18758) `dags tests` and `tasks tests` should not leave any traces in the DB in DagRun table (even if `dags tests` conceptually run backfill, it used DebugExecutor and - as far as I remember at least, did not rely on the DB entries). Or at least that was the intention.. -- 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]
