The GitHub Actions job "Tests (ARM)" on airflow.git/v3-3-test has failed. Run started by GitHub user vatsrahul1001 (triggered by vatsrahul1001).
Head commit for run: 47e4241558bef5eac6d2c8c3e5e5718c13f79d2f / Amogh Desai <[email protected]> Add support for pandas 3 based xcoms in airflow (#71103) (#71169) * Keep DataFrame XComs working on pandas 3 pandas 3 exposes its public classes from the `pandas` namespace, so a DataFrame is now qualified as `pandas.DataFrame` rather than `pandas.core.frame.DataFrame`. The serializer was registered only under the old name, so pushing a DataFrame through XCom raised "cannot serialize object of type <class 'pandas.DataFrame'>". Both names are registered so values written by either version stay readable. pandas 3 also infers a str column where it used to infer object, and keeps its missing values as NA instead of stringifying them, which the amazon and salesforce tests asserted on. * Document pandas 3 impact on DataFrame XComs Deployments need to know that every component has to carry the pandas 3 support before pandas 3 reaches any worker, that a rollback strands the XComs written in the meantime, and that a pulled DataFrame now takes its dtypes from the reader's pandas version. * Name the pandas 3 newsfragment after its own pull request * Add regression test for the pandas 2/3 cross-version registry lookup * rename newsfragment file --------- (cherry picked from commit 4091ccf786b80772ba7f32d26ab8de01d79b7776) Co-authored-by: Jarek Potiuk <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/31028701079 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
