Thank you so much Neal for bringing this up. I was merging PRs without realizing about this change. :/
Fun stuff, great timing with the release coming up. A quick fix for now is to check the corresponding branch on the user's fork. For example, this PR <https://github.com/apache/arrow/pull/9032> has a corresponding branch on my user <https://github.com/jorgecarleitao/arrow/tree/bench_alloc> which triggered all our jobs here <https://github.com/jorgecarleitao/arrow/actions/runs/449186700>. There are two things to keep in mind with this approach: 1. There are some github jobs that are conditional to be on the main repo, and those won't be triggered 2. we can't rely on the check-mark on the UI on the PR page Best, Jorge On Mon, Dec 28, 2020 at 7:49 PM Neal Richardson <neal.p.richard...@gmail.com> wrote: > Hi all, > It appears that INFRA has decided to block GitHub actions that are not > owned by github or apache: > https://issues.apache.org/jira/browse/INFRA-21234 > > This means that none of our C++, Rust, R, or Julia builds are currently > running. > > INFRA seems to have an allowlist, and I have petitioned to have our blocked > actions allowed: https://issues.apache.org/jira/browse/INFRA-21239 > > Until this is resolved, we will need to rely on on-demand crossbow builds, > or we may want to hold off merging patches that have changes in the > affected languages. > > Speaking of crossbow, on an unrelated note, it seems that our nightly > builds were disabled last week by GitHub due to inactivity on the master > branch of ursa-labs/crossbow (even though the repo has >32,000 branches). I > clicked the magic button in github to re-enable them, so hopefully we'll > start seeing nightly build report emails again tomorrow. > > Neal >
