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 ratio. For one current example, there's currently an R valgrind build that fails, and it's been (mostly) isolated + we have a Jira to fix it [1], and that's in progress/in someone's work queue. Being able to tie that information to the continued failure will (hopefully) help us both prioritize fixing it and help us identify which of the failures are new + novel and need debugging attention.
Reliability over the past 7 or 30 days would be fantastic (I created [2] to track that). Along with information about when the first (sustained) failure was (which also already has a ticket [3]). Those two would help a ton! [1] https://issues.apache.org/jira/browse/ARROW-12708 [2] https://issues.apache.org/jira/browse/ARROW-12862 [3] https://issues.apache.org/jira/browse/ARROW-12821 -Jon On Mon, May 24, 2021 at 3:54 PM Wes McKinney <wesmck...@gmail.com> wrote: > > 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 broken builds and the reliability of each > build over the trailing 7 or 30 days would be useful. Knowing that a > particular build is only passing 20% of the time would help steer our > efforts. > > On Mon, May 24, 2021 at 2:49 PM Sutou Kouhei <k...@clear-code.com> wrote: > > > > 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 and nightly build report e-mails are sent only > > when one more nightly builds are failed, nightly build > > report will not be noisy. > > > > Constant nightly build failures aren't healthy. It may block > > a new release. Can we work on keeping green nightly build? I > > think that we need to fix failing jobs and remove > > unmaintained failing jobs for it. > > > > > > Thanks, > > -- > > kou > > > > In <cajpuwmdjnjdr82paew-dysiw9bdiblwqh1dotyut8c4tktv...@mail.gmail.com> > > "Re: Moving automated nightly build e-mails to a separate mailing list" > > on Mon, 24 May 2021 11:22:46 -0700, > > Wes McKinney <wesmck...@gmail.com> wrote: > > > > > 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 > > > <mavarga...@uc.cl.invalid> wrote: > > >> > > >> 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 > > >> <szucs.kriszt...@gmail.com> > > >> wrote: > > >> > > >> > 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, May 24, 2021 at 4:01 PM Wes McKinney <wesmck...@gmail.com> > > >> > wrote: > > >> > > > > >> > > 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 < > > >> > szucs.kriszt...@gmail.com> > > >> > > wrote: > > >> > > > > >> > > > On Sun, May 23, 2021 at 7:30 PM Wes McKinney <wesmck...@gmail.com> > > >> > 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 Sun, May 23, 2021 at 10:12 AM Mauricio Vargas > > >> > > > > <mavarga...@uc.cl.invalid> wrote: > > >> > > > > > > > >> > > > > > hi > > >> > > > > > > > >> > > > > > I agree with this, and being the person who has been digging > > >> > > > > > into > > >> > > > nightly > > >> > > > > > errors, I can move this to a weekly email to builds@ > > >> > > > > > > > >> > > > > > > > >> > > > > > On Sun, May 23, 2021 at 11:14 AM Wes McKinney > > >> > > > > > <wesmck...@gmail.com > > >> > > > > >> > > > wrote: > > >> > > > > > > > >> > > > > > > hi folks, > > >> > > > > > > > > >> > > > > > > In an effort to increase the signal-to-noise ratio on dev@, I > > >> > > > suggest > > >> > > > > > > that we move the [NIGHTLY] e-mails to a separate > > >> > > > > > > bui...@arrow.apache.org e-mail address (or similarly named). > > >> > Having > > >> > > > > > > them on a mailing list makes it easy for us to see them when > > >> > > > > > > we > > >> > want > > >> > > > > > > to see them, but otherwise for many it's an e-mail filter to > > >> > > > > > > be > > >> > set > > >> > > > up > > >> > > > > > > when you first subscribe to dev@. > > >> > > > > > > > > >> > > > > > > Thoughts? Would someone like to implement this change? > > >> > > > > > > > > >> > > > > > > Thanks, > > >> > > > > > > Wes > > >> > > > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > -- > > >> > > > > > — > > >> > > > > > *Mauricio 'Pachá' Vargas Sepúlveda* > > >> > > > > > Site: pacha.dev > > >> > > > > > Blog: pacha.dev/blog > > >> > > > > > >> > > > >> > > >> > > >> -- > > >> — > > >> *Mauricio 'Pachá' Vargas Sepúlveda* > > >> Site: pacha.dev > > >> Blog: pacha.dev/blog
