I'm seeing issues with a bad signature on Centos binaries (I had to
regenerate some files here because my signature was initially missing from
the dev KEYS file). Can anyone else confirm?
Also, for Debian and Ubuntu I'm seeing warnings about not being able to
verify the identify of my signature (
Hello,
I suggest we tackle https://jira.apache.org/jira/browse/ARROW-5801.
For Rust, that would be
https://jira.apache.org/jira/browse/ARROW-5809. Once ported to
docker/docker-compose, it's trivial to activate github action for the
same test (see https://github.com/apache/arrow/pull/5530). As I'm
Andy Grove created ARROW-6731:
-
Summary: [CI] [Rust] Set up Github Action to run Rust tests
Key: ARROW-6731
URL: https://issues.apache.org/jira/browse/ARROW-6731
Project: Apache Arrow
Issue Type:
Francois Saint-Jacques created ARROW-6730:
-
Summary: [CI] Use Github Actions for "C++ with clang 7" docker
image
Key: ARROW-6730
URL: https://issues.apache.org/jira/browse/ARROW-6730
Project:
@David -- the macOS conda-based build is a bit finicky due to the
SDK-related issues. In any case since we can successfully produce
macOS binaries for Homebrew and wheel/conda, that's the most important
thing, though we should aim for a more refined out-of-the-box
development experience
Not sure i
Pasha Stetsenko created ARROW-6729:
--
Summary: StlStringBuffer constructor is not zero-copy
Key: ARROW-6729
URL: https://issues.apache.org/jira/browse/ARROW-6729
Project: Apache Arrow
Issue T
On Fri, Sep 27, 2019 at 5:07 PM Andy Grove wrote:
> Thanks Krisztian. That's very helpful. I will create a CI page on the wiki
> and add this info.
>
> Does anyone have any objections to me trying out GitHub Actions for running
> the Rust tests on PR builds? I could try this out on my own fork fi
Eric Erhardt created ARROW-6728:
---
Summary: [C#] Support reading and writing Date32 and Date64 arrays
Key: ARROW-6728
URL: https://issues.apache.org/jira/browse/ARROW-6728
Project: Apache Arrow
Thanks Krisztian. That's very helpful. I will create a CI page on the wiki
and add this info.
Does anyone have any objections to me trying out GitHub Actions for running
the Rust tests on PR builds? I could try this out on my own fork first.
On Fri, Sep 27, 2019 at 7:40 AM Krisztián Szűcs
wrote:
>
> I checked in the key to https://dist.apache.org/repos/dist/release/arrow/.
> Is there something else I need to do to make it available for verification?
To answer my own question I think I missed adding them to the the dev
branch (I just did this so hopefully they will propagate soon).
On Fri
>
> I found that Micah's GPG key did not seem to be in KEYS and had to
> import it manually.
I checked in the key to https://dist.apache.org/repos/dist/release/arrow/.
Is there something else I need to do to make it available for verification?
On Fri, Sep 27, 2019 at 7:45 AM Andy Grove wrote:
On Fri, Sep 27, 2019 at 4:02 PM Crossbow wrote:
>
> Arrow Build Report for Job nightly-2019-09-27-0
>
> All tasks:
> https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-09-27-0
>
> Failed Tasks:
> - debian-stretch:
> URL:
> https://github.com/ursa-labs/crossbow/branches/all?qu
Krisztian Szucs created ARROW-6727:
--
Summary: [Crossbow] Improve the GitHub asset uploading prevent
GitHub timeouts
Key: ARROW-6727
URL: https://issues.apache.org/jira/browse/ARROW-6727
Project: Apac
Arrow Build Report for Job nightly-2019-09-27-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-09-27-0
Failed Tasks:
- debian-stretch:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2019-09-27-0-azure-debian-stretch
- docker-cpp-fuzzi
Krisztian Szucs created ARROW-6726:
--
Summary: [CI] Figure out how to run reliably the fuzzit task
Key: ARROW-6726
URL: https://issues.apache.org/jira/browse/ARROW-6726
Project: Apache Arrow
Krisztian Szucs created ARROW-6725:
--
Summary: [CI] Disable 3rdparty fuzzit nightly builds
Key: ARROW-6725
URL: https://issues.apache.org/jira/browse/ARROW-6725
Project: Apache Arrow
Issue Ty
Agree, I'll create a PR and an issue to revisit the fuzzit integration.
On Thu, Sep 26, 2019 at 9:24 PM Wes McKinney wrote:
> Should we disable the fuzzit job? This is for a third party CI-type
> service, so the failure here seems like it's adding unneeded noise
>
> On Thu, Sep 26, 2019 at 12:31
+1 for Rust implementation. Tests run fine out the box. Version numbers are
correct.
On Fri, Sep 27, 2019 at 7:26 AM David Li wrote:
> I ran the source verification script on MacOS 10.12 (Sierra).
>
> I found that Micah's GPG key did not seem to be in KEYS and had to
> import it manually.
>
> Py
On Fri, Sep 27, 2019 at 3:25 PM Andy Grove wrote:
> I've been poking around on the Arrow website and wiki and I can't find
> documentation relating to CI. Do we have any documentation on how things
> work today or what the goals are?
I don't think so.
> For Rust builds it isn't immediately
> ob
There are a bunch of other mailing list discussions over the last few
months I recommend digging up and reviewing.
As one practical issue with the Ursabot builds, those are running on
servers that are hosted at my physical home in Nashville. If there's a
power outage https://ci.ursalabs.org and al
I ran the source verification script on MacOS 10.12 (Sierra).
I found that Micah's GPG key did not seem to be in KEYS and had to
import it manually.
Python failed in pyarrow/tests/test_cython.py::test_cython_api when
invoking gcc. Is this the MacOS conda toolchain issue? It works if I
add `-stdli
I've been poking around on the Arrow website and wiki and I can't find
documentation relating to CI. Do we have any documentation on how things
work today or what the goals are? For Rust builds it isn't immediately
obvious why they are building on both Travis CI and Ursabot.
On Fri, Sep 27, 2019
Wes McKinney created ARROW-6724:
---
Summary: [C++] Add simpler static ctor for BufferOutputStream than
the current Create function
Key: ARROW-6724
URL: https://issues.apache.org/jira/browse/ARROW-6724
Pro
I've been sounding the alarm bells about this for a while. We need to
work to get ourselves off of Travis CI, but it is not going to be
easy.
On Thu, Sep 26, 2019 at 11:42 PM Micah Kornfield wrote:
>
> My understanding is the Travis CI queue is shared among all apache
> projects, and there are fe
FYI, using the kibble.dev link from INFRA-18533, it seems that this
September we're using about 15% of the ASF's total Travis CI capacity
(60 concurrent workers I think)
https://imgur.com/a/oOrbPsj
The highest is Apache Druid (incubating) at 18%, so we are #2. Suffice
to say the ASF's Travis coul
Dear all,
When releasing an ArrowBuf, we will run the following piece of code:
private int decrement(int decrement) {
allocator.assertOpen();
final int outcome;
synchronized (allocationManager) {
outcome = bufRefCnt.addAndGet(-decrement);
if (outcome == 0) {
lDestructionTi
Liya Fan created ARROW-6723:
---
Summary: [Java] Reduce the range of synchronized block when
releasing an ArrowBuf
Key: ARROW-6723
URL: https://issues.apache.org/jira/browse/ARROW-6723
Project: Apache Arrow
Liya Fan created ARROW-6722:
---
Summary: [Java] Provide a uniform way to get vector name
Key: ARROW-6722
URL: https://issues.apache.org/jira/browse/ARROW-6722
Project: Apache Arrow
Issue Type: Improv
Ji Liu created ARROW-6721:
-
Summary: [JAVA] Avro adapter benchmark only runs once in JMH
Key: ARROW-6721
URL: https://issues.apache.org/jira/browse/ARROW-6721
Project: Apache Arrow
Issue Type: Bug
Hi,
I would like to propose the following release candidate (RC1) of Apache
Arrow version 0.15.0. This is a release consisting of 672
resolved JIRA issues[1]. (RC0 was aborted due to release script issues).
This release candidate is based on commit:
77f091888dbe5a4e023a66b986a2dd474696061a [
30 matches
Mail list logo