https://builds.apache.org/job/log4j/job/master/53/testReport/

Would be nice to get this email that Jenkins sends to include the list
of failed tests, but it's all there at least.

On Fri, 17 Apr 2020 at 15:28, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>
> What test? From what I could see the build had finished.
>
> Ralph
>
> > On Apr 17, 2020, at 11:02 AM, Matt Sicker <boa...@gmail.com> wrote:
> >
> > This test has been flaky on Jenkins. I used the simplest pipeline
> > possible here. If these failures are specific to a particular Jenkins
> > node, then that might be something we can adjust. Otherwise, this test
> > might be buggy.
> >
> > On Fri, 17 Apr 2020 at 12:43, Ralph Goers <ralph.go...@dslextreme.com> 
> > wrote:
> >>
> >> Matt,
> >>
> >> Once again the build is failing for no reason I can understand. How can we 
> >> maintain this if you are the only one who knows how it works?
> >>
> >> Ralph
> >>
> >>> On Apr 17, 2020, at 1:09 AM, Mr. Jenkins <jenk...@builds.apache.org> 
> >>> wrote:
> >>>
> >>>
> >>> There is a build failure in log4j/master.
> >>>
> >>> Build: https://builds.apache.org/job/log4j/job/master/53/
> >>> Logs: https://builds.apache.org/job/log4j/job/master/53/console
> >>> Changes: https://builds.apache.org/job/log4j/job/master/53/changes
> >>>
> >>> --
> >>> Mr. Jenkins
> >>> Director of Continuous Integration
> >>
> >>
> >
> >
> > --
> > Matt Sicker <boa...@gmail.com>
> >
>
>


-- 
Matt Sicker <boa...@gmail.com>

Reply via email to