Hello, I am part of a team that is working on an Arrow fork, working on an enhancement to the C++ implementation of Parquet Modular Encryption.
We have been seeing a lot of failing github actions and want to understand these better. We created a fresh fork off of the most recent Arrow release (22.0, commit 5eabf), and then just added a comment to each file that we touch on our project. No functionality was modified. The purpose of this is to trigger all actions that our code changes will eventually trigger, but from a stable version. However, even from the stable version, we have noticed plenty of actions failing. This is a run of the actions: https://github.com/sofia-tekdatum/arrow-22/actions/runs/19181753453/job/54839949581?pr=2 This is the PR (as you will see, we only added comments to a subset of files) https://github.com/sofia-tekdatum/arrow-22/pull/1 Most of the failing actions are Ruby-related, but there are a few other types in there as well. If necessary, we can characterize/summarize the failures in depth. Our main question here: is there a reason for a stable version with no virtually no changes shows a relatively high number of Github action failures (such as the ones above)? Regards, Marco Arguedas
