hi Francois, I updated the CI failure page https://cwiki.apache.org/confluence/display/ARROW/Continuous+Integration+failures to split the resolved issues out into a separate filter. This makes things clearer and we can see now there are 7 open issues in the filter
I also changed the language a bit since describing these issues as "false positive" could be misleading -- some of these things are legitimate bugs and may simply present as a flaky test in practice. - Wes On Mon, Mar 4, 2019 at 9:11 AM Francois Saint-Jacques <fsaintjacq...@gmail.com> wrote: > > Hello, > > I created a new label named `ci-failure`, which was retroactively applied > to most issues triggering a CI failure in other PRs/master (I searched for > travis-ci.org/apache/arrow and tagged them). The goal here is to track > issues which generates false positives failure in PRs and ideally minimize > this and/or give a very high priority to resolve. > > The following dashboard > https://cwiki.apache.org/confluence/display/ARROW/Continuous+Integration+failures > tracks all task with the `ci-failure` label. > > I also took the opportunity to tidy the top level navigation page tree, > notably > - created a Releases page and moved all release pages > - created a Dashboards page and moved all related pages > - created a Developers page and moved all related pages > - Ordered page in importance for new users, e.g. contribute & release at > top, moved all committer/maintainer stuff in the lower part > > François > > On Sat, Mar 2, 2019 at 5:53 PM Wes McKinney <wesmck...@gmail.com> wrote: > > > I just gave you edit access. > > > > If any PMC member would like to be an admin on the Confluence space > > (and you are not already), please let me know and I'll add you so you > > can help with the wiki admin requests > > > > On Fri, Mar 1, 2019 at 8:09 PM Francois Saint-Jacques > > <fsaintjacq...@gmail.com> wrote: > > > > > > Could someone give me write/edit access to confluence? > > > > > > Thank you, > > > François > > > > > > On Fri, Mar 1, 2019 at 3:55 PM Francois Saint-Jacques < > > > fsaintjacq...@gmail.com> wrote: > > > > > > > I'll take this. > > > > > > > > On Fri, Mar 1, 2019 at 3:55 PM Wes McKinney <wesmck...@gmail.com> > > wrote: > > > > > > > >> We could create a page on the wiki that shows all open and resolved > > > >> issues relating to unexpected CI / build failures. Would someone like > > > >> to give this a go? There are probably many historical issues that can > > > >> be tagged with the label > > > >> > > > >> On Fri, Mar 1, 2019 at 12:45 PM Francois Saint-Jacques > > > >> <fsaintjacq...@gmail.com> wrote: > > > >> > > > > >> > I agree with adding a tag/label for this and even marking the > > failure as > > > >> > critical. > > > >> > > > > >> > > > > >> > On Fri, Mar 1, 2019 at 12:18 PM Micah Kornfield < > > emkornfi...@gmail.com> > > > >> > wrote: > > > >> > > > > >> > > Moving away from the tactical for a minute, I think being able to > > > >> track > > > >> > > these over time would be useful. I can think of a couple of high > > > >> level > > > >> > > approaches and I was wondering what others think. > > > >> > > > > > >> > > 1. Use tags appropriately in JIRA and try to generate a report > > from > > > >> that. > > > >> > > 2. Create a new confluence page to try to log each time these > > occur > > > >> (and > > > >> > > route cause). > > > >> > > 3. A separate spreadsheet someplace (e.g. Google Sheet). > > > >> > > > > > >> > > Thoughts? > > > >> > > > > > >> > > -Micah > > > >> > > > > > >> > > > > > >> > > On Fri, Mar 1, 2019 at 8:55 AM Francois Saint-Jacques < > > > >> > > fsaintjacq...@gmail.com> wrote: > > > >> > > > > > >> > > > Also just created > > https://issues.apache.org/jira/browse/ARROW-4728 > > > >> > > > > > > >> > > > On Thu, Feb 28, 2019 at 3:53 AM Ravindra Pindikura < > > > >> ravin...@dremio.com> > > > >> > > > wrote: > > > >> > > > > > > >> > > > > > > > >> > > > > > > > >> > > > > > On Feb 28, 2019, at 2:10 PM, Antoine Pitrou < > > anto...@python.org > > > >> > > > > >> > > > wrote: > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > Le 28/02/2019 à 07:53, Ravindra Pindikura a écrit : > > > >> > > > > >> > > > >> > > > > >> > > > >> > > > > >>> On Feb 27, 2019, at 1:48 AM, Antoine Pitrou < > > > >> solip...@pitrou.net> > > > >> > > > > wrote: > > > >> > > > > >>> > > > >> > > > > >>> On Tue, 26 Feb 2019 13:39:08 -0600 > > > >> > > > > >>> Wes McKinney <wesmck...@gmail.com> wrote: > > > >> > > > > >>>> hi folks, > > > >> > > > > >>>> > > > >> > > > > >>>> We haven't had a green build on master for about 5 days > > now > > > >> (the > > > >> > > > last > > > >> > > > > >>>> one was February 21). Has anyone else been paying > > attention > > > >> to > > > >> > > this? > > > >> > > > > >>>> It seems we should start cataloging which tests and build > > > >> > > > environments > > > >> > > > > >>>> are the most flaky and see if there's anything we can do > > to > > > >> reduce > > > >> > > > the > > > >> > > > > >>>> flakiness. Since we are dependent on anaconda.org for > > build > > > >> > > > toolchain > > > >> > > > > >>>> packages, it's hard to control for the 500 timeouts that > > > >> occur > > > >> > > > there, > > > >> > > > > >>>> but I'm seeing other kinds of routine flakiness. > > > >> > > > > >>> > > > >> > > > > >>> Isn't it https://issues.apache.org/jira/browse/ARROW-4684 > > ? > > > >> > > > > >> > > > >> > > > > >> ARROW-4684 seems to be failing consistently in travis CI. > > > >> > > > > >> > > > >> > > > > >> Can I merge a change if this is the only CI failure ? > > > >> > > > > > > > > >> > > > > > Yes, you can. > > > >> > > > > > > > >> > > > > Thanks ! > > > >> > > > > > > > >> > > > > > > > > >> > > > > > Regards > > > >> > > > > > > > > >> > > > > > Antoine. > > > >> > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > > >
