Duplicate macOS ARM migrator PRs for deltalake

[jakirkham]

After adding deltalake to the macOS ARM migration ( conda-forge/conda-forge-pinning-feedstock#5483 ), the bot opened a migration PR and then ~1hr later opened another one. Here are the PRs

• ARM OSX Migrator conda-forge/deltalake-feedstock#25
• ARM OSX Migrator conda-forge/deltalake-feedstock#26

Some things to note:

• The feedstock has only one branch
• Both PRs target main
• Both PRs were opened today ~1hr apart
• No other changes occurred to main today

Was there some kind of hiccup in the bot?

[jaimergp]

I observed this today but with a version update:

• constructor v3.7.0 conda-forge/constructor-feedstock#74
• constructor v3.7.0 conda-forge/constructor-feedstock#75

[beckermr]

Yes I think I know the cause. GHA is killing some bot jobs due to disk usage and so they are not deploying their changes to the graph.

If you all know of a way to delete some data on the runners, that'd be cool. We should also figure out what is taking so much space.

[jakirkham]

The conda-smithy GHA purge logic works pretty well

[jakirkham]

Should add have seen the same issue Jaime has in a few places. For example:

• google-cloud-orchestration-airflow v1.12.1 conda-forge/google-cloud-orchestration-airflow-feedstock#22
• google-cloud-orchestration-airflow v1.12.1 conda-forge/google-cloud-orchestration-airflow-feedstock#23