I also very much agree with all of the sentiments above.
One of the things that I'm hoping this new site/dashboard/whatever we
come up with will have is some more information / context around the
failures that hopefully will help make them less overwhelming and have
a higher signal to noise
I agree strongly with this sentiment. The idea of e-mailing only when
there are failed builds was to motivate us to fix the builds. In
practice this is not happening unfortunately. Having a website
dashboard showing build health over time along with a ~ weekly e-mail
to dev@ indicating currently
Hi,
I agree with the fact that current nightly build report is
noisy and reporting as HTML on website improves
readability. But I think that the real problem is not caused
by them. It's the real problem that we always have failed
nightly build jobs. If we sometimes have failed nightly
build jobs
OK. bui...@arrow.apache.org is now ready to use, so can someone please
take care of moving the nightly e-mails there and confirm here when
that's completed?
https://lists.apache.org/list.html?bui...@arrow.apache.org
On Mon, May 24, 2021 at 10:40 AM Mauricio Vargas
wrote:
>
> yes, i strongly
I have been working with other committers to have the Gandiva PRs merged.
What you see is the backlog of PRs that need to be merged after the review
by Projjal.
On Mon, May 24, 2021 at 11:21 PM Will Jones wrote:
> Hello,
>
> Following up on this. Thanks to Projjal for reviewing so many PRs! One
Hello,
Following up on this. Thanks to Projjal for reviewing so many PRs! One
issue is it doesn't look like Projjal is a committer and thus those PRs are
not shown as mergeable.
Here are some PRs that looks like they should be ready to merge:
- ARROW-11342
yes, i strongly agree with this idea
i was preparing a static site last week taht I plan to show on wednesday
On Mon, May 24, 2021 at 11:13 AM Krisztián Szűcs
wrote:
> We could generate a static website on the crossbow github page
> including more details about the failures - this would keep
We could generate a static website on the crossbow github page
including more details about the failures - this would keep crossbow
self-contained.
I'd suggest still sending the failing builds on the new mailing list
(including the static page's link), so we get notified by the
failures.
On Mon,
Frankly I think we should move these reports to a real website rather than
sending these emails. The emails to me were always a stopgap to add some
visibility where there previously was little (you had to go digging on
crossbow).
On Mon, May 24, 2021 at 2:01 AM Krisztián Szűcs
wrote:
> On Sun,
+1 (binding)
Verified the source, binaries and wheels locally on macOS Big Sur (Intel).
The automatized verification tasks have passed as well with some
modifications [1].
[1]: https://github.com/apache/arrow/pull/10374
Thanks, Krisztian
On Sat, May 22, 2021 at 9:52 PM Sutou Kouhei wrote:
>
>
Arrow Build Report for Job nightly-2021-05-24-0
All tasks:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-05-24-0
Failed Tasks:
- conda-linux-gcc-py37-arm64:
URL:
On Sun, May 23, 2021 at 7:30 PM Wes McKinney wrote:
>
> I just requested builds@ to be created on the self-service platform.
Hi,
Having a separate list sounds like a good idea to me.
Could we enable HTML emails on that list?
See jira https://issues.apache.org/jira/browse/ARROW-12822
>
>
> On
12 matches
Mail list logo
