The GitHub Actions job "Tests (AMD)" on 
airflow.git/batch-parse-result-persistence has succeeded.
Run started by GitHub user ephraimbuddy (triggered by ephraimbuddy).

Head commit for run:
770e20b7a0fa89edba7f71918183c25ea20c7578 / Ephraim Anierobi 
<[email protected]>
Stop a batched sweep leaving stale a Dag it had just written

An import error is recorded against a file after the Dags filed under that file
are written, so a file reporting an error and a file whose Dag is filed under it
could not share a write: the error marked the Dag stale, hiding it from the
scheduler and the UI until something parsed it again. Grouping already held the
two apart in one direction and not the other.

Working out how to group a sweep reads the Dags a parser sent, so a malformed 
one
took the whole cycle down with it rather than the file that carried it. That is
the failure the step before it was already hardened against.

A file handled on its own was written through the seam being deprecated rather
than the one deployments are told to move to, so a deployment that had moved
found its results in the metadata DB anyway.

Two tests added a bundle of the same name without either removing it, so 
whichever
ran second failed on a suite that runs them in a random order.

A group is one transaction only while the metadata database is the only thing
written; the FAB auth manager commits Dag permissions partway through one. Said
where the retry that assumes otherwise is documented.

Report URL: https://github.com/apache/airflow/actions/runs/32250329713

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to