Hi Thorsten,
Would you consider a PR that updated the failing tests with code to check
for the required programmes?
We could then output a failure message that informed the user why the test
does not work.
On Fri, Jul 17, 2020 at 8:57 PM Thorsten Schöning
wrote:
> Guten Tag Robert Middleton,
>
Please let me know if I can help with that - if you're using the new build
process I made and something doesn't work as expected, I'm happy to help.
On July 18, 2020 02:58:03 Matt Sicker wrote:
I've finished migrating all our jobs that I could find. There's a
log4net pipeline that I could po
I've finished migrating all our jobs that I could find. There's a
log4net pipeline that I could potentially enable in the new CI, but
the Windows node doesn't seem to be working quite yet.
On Thu, 16 Jul 2020 at 12:36, Matt Sicker wrote:
>
> Here’s the answer to my previous forward. I can look in
As you can see, I've figured out how to provide a more useful email in
response to the builds. I've also done the same for the other builds
so far.
On Fri, 17 Jul 2020 at 19:31, Mr. Jenkins wrote:
>
> GENERAL INFO
>
> BUILD SUCCESS
> Build URL:
> https://ci-builds.apache.org/job/Logging/job/log4
Well, that should've been text instead of html. Oops.
On Fri, 17 Jul 2020 at 19:07, Mr. Jenkins wrote:
>
>
> BODY, TABLE, TD, TH, P {
> font-family: Calibri, Verdana, Helvetica, sans serif;
> font-size: 12px;
> color: black;
> }
> .console {
> font-family: Courier New;
>
I guess I'm viewing this as an "optional" test - we know that the test
is going to fail(because e.g. we don't have gzip installed), so
there's no reason to run the test. If gzip is installed, then the
test should run and pass appropriately.
I definitely agree that developers should have all tests
Guten Tag Robert Middleton,
am Donnerstag, 16. Juli 2020 um 14:54 schrieben Sie:
> So perhaps the best solution is based a little bit off of Stephen's
> earlier PR(#18[1]), but instead of compiling out the code that depends
> on gzip we make the test more granular(one test for rolling zip, one
> t
Hi Ralph, **
*Per the JDK 15 schedule, we are in Rampdown Phase Two* *[1]*
Per the JDK Release Process [2] we now turn our focus to *P1 and P2
bugs*, which can be fixed with approval [3].
Late enhancements are still possible, with approval [4], but the bar is
now extraordinarily high.
**Ple
