Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Remko Popma
Thanks for the quick turnaround Ralph! > On Jun 26, 2019, at 11:55, Matt Sicker wrote: > > Thanks Ralph! > >> On Tue, Jun 25, 2019 at 21:20, Gary Gregory wrote: >> >> I will test when it becomes available... :-) >> >> Gary >> >> On Tue, Jun 25, 2019 at 9:34 PM Ralph Goers >> wrote: >> >>

[VOTE] Release Log4j 2.12.0-rc2

2019-06-25 Thread Ralph Goers
This is a vote to release Log4j 2.12.0, the next version of the Log4j 2 project. Please download, test, and cast your votes on the log4j developers list. [] +1, release the artifacts [] -1, don't release because... The vote will remain open for 72 hours (or more if required). All votes are welco

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Matt Sicker
Thanks Ralph! On Tue, Jun 25, 2019 at 21:20, Gary Gregory wrote: > I will test when it becomes available... :-) > > Gary > > On Tue, Jun 25, 2019 at 9:34 PM Ralph Goers > wrote: > > > I will see if I can get a new rc out tonight, but it might not make it. > > > > Ralph > > > > > On Jun 25, 2019

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Gary Gregory
I will test when it becomes available... :-) Gary On Tue, Jun 25, 2019 at 9:34 PM Ralph Goers wrote: > I will see if I can get a new rc out tonight, but it might not make it. > > Ralph > > > On Jun 25, 2019, at 6:26 PM, Gary Gregory > wrote: > > > > On Tue, Jun 25, 2019 at 8:55 PM Ralph Goers

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Ralph Goers
I will see if I can get a new rc out tonight, but it might not make it. Ralph > On Jun 25, 2019, at 6:26 PM, Gary Gregory wrote: > > On Tue, Jun 25, 2019 at 8:55 PM Ralph Goers > wrote: > >> I have committed the fix and verified it works in my Windows VM. >> > > That fixes it for me as well

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Gary Gregory
On Tue, Jun 25, 2019 at 8:55 PM Ralph Goers wrote: > I have committed the fix and verified it works in my Windows VM. > That fixes it for me as well with the HEAD of the 2.x branch and Windows 10.0.16299.1087 Gary > > Ralph > > > On Jun 25, 2019, at 5:34 PM, Ralph Goers > wrote: > > > > This

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Ralph Goers
I have committed the fix and verified it works in my Windows VM. Ralph > On Jun 25, 2019, at 5:34 PM, Ralph Goers wrote: > > This release vote is cancelled. > > I have been able to duplicate the problem in my Windows VM. I believe I know > what the problem is and will be testing it shortly. T

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Ralph Goers
This release vote is cancelled. I have been able to duplicate the problem in my Windows VM. I believe I know what the problem is and will be testing it shortly. The problem is not with the test. Ralph > On Jun 25, 2019, at 4:01 PM, Remko Popma wrote: > > When building from the tag on my Wind

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Remko Popma
When building from the tag on my Windows laptop, I get the same errors that Gary was seeing: [ERROR] Failures: [ERROR] QueueFullAsyncLoggerConfigLoggingFromToStringTest.testLoggingFromToStringCausesOutOfOrderMessages:76->asyncLoggerConfigRecursiveTest:96 expected:<...ging in toString() #[0]> but w

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Ralph Goers
Interesting. It is failing trying to cleanup files before running the next test. This seems likely to be something wrong in the unit test rather than something wrong with ResolverUtil. However, ResolverUtilTest hasn’t changed in quite a while. If this is the only problem I am reluctant to resp

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Gary Gregory
Here we go: [INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @ log4j-core --- [INFO] Surefire report directory: C:\temp\rc\logging-log4j2\log4j-core\target\surefire-reports [INFO] parallel='none', perCoreThreadCount=true, threadCount=0, useUnlimitedThreads=false, threadCountSuites=0, th

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Gary Gregory
I will retest and report back today... Gary On Tue, Jun 25, 2019, 10:51 Ralph Goers wrote: > Can you run just that test to see if you get stack traces? > > Ralph > > > On Jun 25, 2019, at 6:59 AM, Gary Gregory > wrote: > > > > Oops, hit send too soon. I get the test failures: > > > > ... > > [

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Matt Sicker
Oh wow I forgot about the multi-JDK setup. I'm too much of a Windows noob to figure that out at the moment. I typically install a JDK into Windows Server using Chocolatey (package manager) because it's pretty hard to download and install applications without a bunch of server config first that I do

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Ralph Goers
Can you run just that test to see if you get stack traces? Ralph > On Jun 25, 2019, at 6:59 AM, Gary Gregory wrote: > > Oops, hit send too soon. I get the test failures: > > ... > [ERROR] Failures: > [ERROR] ResolverUtilTest.testExtractPathFromFileUrl > target\testpluginsutil failed with jav

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Matt Sicker
Oh no, those are Windows specific failures! I’ll try reproducing in Windows Server. On Tue, Jun 25, 2019 at 09:00, Gary Gregory wrote: > Oops, hit send too soon. I get the test failures: > > ... > [ERROR] Failures: > [ERROR] ResolverUtilTest.testExtractPathFromFileUrl > target\testpluginsutil

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Gary Gregory
Oops, hit send too soon. I get the test failures: ... [ERROR] Failures: [ERROR] ResolverUtilTest.testExtractPathFromFileUrl target\testpluginsutil failed with java.nio.file.FileSystemException: target\testpluginsutil\resolverutil2\customplugin2.jar: The process cannot access the file because it

Re: [VOTE] Release Log4j 2.12.0-rc1

2019-06-25 Thread Gary Gregory
I get the following test failures: On Sun, Jun 23, 2019 at 9:43 PM Ralph Goers wrote: > This is a vote to release Log4j 2.12.0, the next version of the Log4j 2 > project. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -1, don't r