I've cleaned up the jenkinsfiles, added links to various things, and
started a wiki page where I can free-form describe anything else that
might be relevant. I also removed a couple things that weren't really
relevant.
On Fri, 17 Apr 2020 at 16:45, Matt Sicker wrote:
>
> Note that you can also br
Note that you can also browse the workspaces for the Windows and
Ubuntu builds to go see what happened. In particular, the workspace
for log4j-osgi on Ubuntu:
https://builds.apache.org/job/log4j/job/master/53/execution/node/17/ws/log4j-osgi/
(might need to log in to see that).
On Fri, 17 Apr 2020
Oh, and the build finished because I added the "-fae" (fail at end)
maven flag so we could get a full test report each time rather than an
abbreviated one.
On Fri, 17 Apr 2020 at 16:10, Matt Sicker wrote:
>
> https://builds.apache.org/job/log4j/job/master/53/testReport/
>
> Would be nice to get t
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 wrote:
>
> What test? From what I could see the build had finished.
>
> Ral
What test? From what I could see the build had finished.
Ralph
> On Apr 17, 2020, at 11:02 AM, Matt Sicker 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
I'll work on writing up some documentation about how this pipeline
works over the weekend.
On Fri, 17 Apr 2020 at 13:02, Matt Sicker 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 th
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 wrote:
>
> Matt,
>
> Once again
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 wrote:
>
>
> There is a build failure in log4j/master.
>
> Build: https://builds.apache.org/job/log
