Arrow Build Report for Job nightly-2021-03-06-0
All tasks:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-03-06-0
Failed Tasks:
- conda-linux-gcc-py39-aarch64:
URL:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-03-06-0-drone-conda-linux
Thanks for the ideas Micah,
I like most of the ideas you have put forth. One way to make some small
step towards this goal might be:
1. Document, as you describe, some guidelines for trivial PRs (I like your
definitions)
2. Update the bot message that requests people to open a JIRA (e.g. [1]) so
t
I stole this one since you said it was fair game :)
https://github.com/apache/arrow/pull/9648/files
PS. Thanks for the content, Neal.
Have a great weekend, folks!
--diana
On Wed, Mar 3, 2021 at 7:12 AM Andy Grove wrote:
>
> I filed https://issues.apache.org/jira/browse/ARROW-11852 to add
Thanks for merging my pull request, Kou! Much appreciated.
But… Now I’m questioning the need for the Contributor role for issue
assignment. Why not just let Arrow tickets be assigned to any user
with a Jira account? Why require the Contributor role?
It’s not like being a “Contributor” on Arrow's
Since we're on the topic of improving the workflow I had a proposal to
consider. Right now the review process is pretty ad-hoc which is fine
but can be a bit tricky to keep track of.
I think it could be improved with a bot to label PRs. The labels would be...
state: failing tests - Any PR start
Hi,
As work in C++ inevitably affects C GLib and Ruby it is necessary for me to be
able to test them locally. I followed instructions here for Macs. Arrow GLib
for developers was installed. However I can not run GLib tests with bundle exec
test/run-test.sh Looks like there might be some path pr
