Oh hey, this one did highlight the failure! Hooray!
Now why does this test fail
On Tue, Aug 25, 2020 at 05:37 Mr. Jenkins
wrote:
> *BUILD UNSTABLE*
>
>
> Build URL
>
> https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/99/
>
>
> Project:
>
> release-2.x
>
>
> Date of build:
>
>
That test sounds like one that fails randomly in CI regardless of which CI
service is used. Makes me wonder where the bug is coming from (test or
library code).
On Tue, Aug 25, 2020 at 06:30 Volkan Yazıcı wrote:
> Problem has been solved after upgrading the Maven wrapper. Now GitHub
>
> Actions
Now that I’ve also stabilized the Jenkins build, I think we should
certainly be paying closer attention to CI failures. I think we can
maintain the dual CI config for now and see if either approach is more
useful for PRs specifically.
On Tue, Aug 25, 2020 at 06:57 Volkan Yazıcı wrote:
> Ralph, e
Yes, you read the subject right! I will appreciate it if people can spare
some time on skimming through the change set one last time regarding JTL.
So... When are we gonna cut the ribbon for the upcoming 2.x release?
Ralph, even though I am pretty new in the team, I want to step up and state
that we *do* need them. CI is really convenient to in-take PRs and confirm
the validity on multiple systems. (I vividly recall the bug surfacing on
Windows and that was exposed by Jenkins.) Or let me put it the other way
ar
Problem has been solved after upgrading the Maven wrapper. Now GitHub
Actions can issue a successful "./mvnw verify" for both master and
release-2.x branches! 🥳 🎉
Even though "verify" succeeds, for some reason test reports still point to
certain errors. See the latest successful builds on master
<
Done -- both on master and release-2.x branches.
*Artifact Id:* log4j-layout-json-template → log4j-layout-template-json
*Package:* org.apache.logging.log4j.layout.json.template →
org.apache.logging.log4j.layout.template.json
On Thu, Aug 20, 2020 at 4:48 PM Carter Kozak wrote:
> Thanks, Volkan!
