Hi Gavin, > I haven't; and I see the error continues, let me investigate further.
The error continues. Would you check these? https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/173/console https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/174/console Thanks, Akira On Fri, Jun 12, 2020 at 4:51 AM Gavin McDonald <gmcdon...@apache.org> wrote: > Hi Akira, > > On Fri, May 22, 2020 at 4:44 AM Akira Ajisaka <aajis...@apache.org> wrote: > > > +CC: common-dev > > > > Hi Gavin, > > > > The job worked as expected in #146 and it helps us to find failed tests > and > > build errors. > > > https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/146/ > > > ack, thanks. > > > > > > > > However, the job itself failed in #147 and #148 by "pipe closed after 0 > > cycles" > > > > > https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/147/console > > > > > https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/148/console > > Have you ever seen this type of error before in other jobs? > > > > I haven't; and I see the error continues, let me investigate further. > > > > > > The QBT job ran full build and full tests. Hadoop has many flaky tests > and > > always some of them fail. > > In addition, there are many other warnings and errors. We have to fix > them > > but it seems the priority is not so high. > > That way the job status is always marked as a failure. > > > > Noted, thanks for the info, as long as it is expected and jobs are being > looked at and not > forgotten, all good :) > > Gav... > > > > > > Thanks, > > Akira > > > > On Fri, May 22, 2020 at 12:23 AM Gavin McDonald <gmcdon...@apache.org> > > wrote: > > > > > Hi, > > > > > > Is there someone here from Hadoop that can look at this job: > > > > > > https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/ > > > > > > It's been failing 'forever' , no success in 148 builds so far that I > can > > > see. > > > > > > I'd like to know if it is something Infra can assist with, maybe > > something > > > is > > > missing in the new setup? > > > > > > It looks like it is build related and not related to the new setup, but > > I'd > > > like to > > > know for sure, and I would like the build fixed, no point it using up > > > resources > > > if nobody is even looking at it. > > > > > > Thanks! > > > > > > Gav... > > > > > >
