Thanks Weston. Regarding jpype, there was a discussion about doing this on
the April 6 nightly build thread:
https://lists.apache.org/thread.html/rc945a730da4b8820cba3b121de02fa165e28c475f1de9ef4a848339f%40%3Cdev.arrow.apache.org%3E

On Sat, Apr 10, 2021 at 2:14 PM Ian Cook <i...@ursacomputing.com> wrote:

> I can confirm that the test-r-minimal-build failure was fixed in
> ARROW-12197.
>
> Ian
>
> On Sat, Apr 10, 2021 at 17:06 Weston Pace <weston.p...@gmail.com> wrote:
>
> > Nightly build triage (based on nightly builds from 4/9):
> >
> > Failed Tasks:
> > - conda-linux-gcc-py36-aarch64:
> >   ARROW-12324 (conda builds timing out, conda slow)
> > - conda-linux-gcc-py37-aarch64:
> >   ARROW-12324 (conda builds timing out, conda slow)
> > - conda-osx-clang-py37-r40:
> >   Appears to have been an intermittent Azure availability error on
> > OSX.  Azure did not report a degradation at the time but they have
> > warned of longer than usual queue times for OSX.  Last several runs of
> > this have passed.
> > - gandiva-jar-ubuntu:
> >   ARROW-12325 (Bug, PR submitted Friday)
> > - test-conda-cpp-valgrind:
> >   ARROW-12320 (Bug in CI configuration, PR submitted and merged.
> > However, I believe this may have been masking an actual error, should
> > check this next nightly run)
> > - test-conda-python-3.7-kartothek-latest:
> >   ARROW-12314 (Integration issue, PR submitted Friday by Joris)
> > - test-conda-python-3.7-kartothek-master:
> >   ARROW-12314 (Integration issue, PR submitted Friday by Joris)
> > - test-conda-python-3.7-pandas-latest:
> >   Segmentation fault on pytest shutdown (no test failures).  I would
> > tentatively attribute it to ARROW-12220 but there is not enough
> > information (e.g. core file) to know for certain.
> > - test-conda-python-3.7-turbodbc-latest:
> >   ARROW-11608 (Uwe Korn volunteered for this, sorry, gentle reminder)
> > - test-conda-python-3.7-turbodbc-master:
> >   ARROW-11608 (Uwe Korn volunteered for this, sorry, gentle reminder)
> > - test-conda-python-3.8-jpype:
> >   ARROW-11146 Build has been failing for a while, there does not
> > appear to be much jpype activity, Neal Richardson suggested asking if
> > we might remove the integration due to lack of interest.  That should
> > follow in a separate discussion.
> > - test-r-minimal-build:
> >   ARROW-12197 (I think, Jonathan Keane can confirm?)
> > - test-r-versions:
> >   ARROW-12208 (Presumably, now that PR is merged we should check)
> > - test-ubuntu-18.04-docs:
> >   ARROW-11633 (This is the intermittent Java failure that has been
> > popping up in CI.  I did some investigation and there may be some
> > options to reduce these failures which I've added to the JIRA)
> > - test-ubuntu-20.04-cpp-thread-sanitizer:
> >   ARROW-12220 (PR submitted)
> >
> > On Fri, Apr 9, 2021 at 8:04 AM Neal Richardson
> > <neal.p.richard...@gmail.com> wrote:
> > >
> > > Looks like we aren't quite ready to release. Nightly build failures
> seem
> > to
> > > have increased rather than decreased, and we're still at 66 open issues
> > on
> > > https://cwiki.apache.org/confluence/display/ARROW/Arrow+4.0.0+Release
> > > despite our work this week (and despite my attempts to bump issues out
> of
> > > scope).
> > >
> > > I strongly encourage you to (1) review your personal backlogs and those
> > of
> > > the languages you maintain and move nonessential features out of the
> 4.0
> > > scope and (2) if you are able, please help triage and fix the nightly
> > > builds.
> > >
> > > Thanks,
> > > Neal
> > >
> > > On Fri, Apr 9, 2021 at 12:33 AM Sutou Kouhei <k...@clear-code.com>
> wrote:
> > >
> > > > Hi,
> > > >
> > > > One more concern:
> > > >
> > > > * ASF's Bintray -> Artifactory migration isn't finished yet.
> > > >
> > > >
> >
> https://lists.apache.org/thread.html/r9200fed3fa812f8c7de07a2500425f258db3231baa8e05f288175e4a%40%3Cbuilds.apache.org%3E
> > > >
> > > >   I think that this is not a blocker. We'll not release
> > > >   deb/rpm packages when we release 4.0. We can release
> > > >   deb/rpm packages later.
> > > >
> > > >
> > > > Thanks,
> > > > --
> > > > kou
> > > >
> > > >
> > > > In <
> caocv4hgknvmd7xvusx2mkisggwh+vtevqxtcyefkg38nki4...@mail.gmail.com
> > >
> > > >   "4.0 release preparation" on Mon, 5 Apr 2021 19:39:30 -0700,
> > > >   Neal Richardson <neal.p.richard...@gmail.com> wrote:
> > > >
> > > > > Hi all,
> > > > > It's release time again. By our quarterly release pace, we are
> > scheduled
> > > > > for an April 4.0.0 release. Given the time it takes to prepare and
> > > > approve
> > > > > a release, I think we should aim to close out our release scope by
> > the
> > > > end
> > > > > of this week, beginning of next at latest, so that we can ensure a
> > > > release
> > > > > around the middle of the month.
> > > > >
> > > > > I have a few concerns, but hopefully they can be resolved in the
> > next few
> > > > > days:
> > > > >
> > > > > * I count 11 nightly build failures on today's run, some of which I
> > swear
> > > > > have been failing every day since the 3.0 release. That's not good.
> > > > > *
> > https://cwiki.apache.org/confluence/display/ARROW/Arrow+4.0.0+Release
> > > > > shows 6 blocking issues, some specifically around packaging and
> > release
> > > > > tooling
> > > > > * The wiki page also shows 157 open, unstarted issues tagged for
> 4.0,
> > > > which
> > > > > seems overly ambitious.
> > > > >
> > > > > Any other concerns? Volunteers to help with some of those specific
> > > > issues?
> > > > >
> > > > > Thanks,
> > > > > Neal
> > > >
> >
>

Reply via email to