Failed tests: 
  ResolverUtilTest.testExtractPathFromJarUrlNotDecodedIfFileExists:49 should 
not be decoded: /home/jenkins/jenkins-slave/workspace/Log4j 
2.x/log4j-core/target/test-classes/log4j config with plus characters.xml
  ResolverUtilTest.testExtractPathFromFileUrlNotDecodedIfFileExists:73 should 
not be decoded: /home/jenkins/jenkins-slave/workspace/Log4j 
2.x/log4j-core/target/test-classes/log4j config with plus characters.xml
  FileUtilsTest.testFileFromUriWithPlusCharactersInName:39 
expected:<log4j[+config+with+plus+]characters.xml> but was:<log4j[ config with 
plus ]characters.xml>

Tests run: 556, Failures: 3, Errors: 0, Skipped: 23


On May 18, 2014, at 6:27 PM, Ralph Goers <[email protected]> wrote:

> I am not sure why Maven said it succeeded.  log4j-core had 3 unit test 
> failures .https://builds.apache.org/view/All/job/Log4j%202.x/919/consoleFull
> Ralph
> 
> On May 18, 2014, at 6:24 PM, Ralph Goers <[email protected]> wrote:
> 
>> The build finished and said it was sending an email to this list.  Let’s see 
>> if it shows up.
>> 
>> Ralph
>> 
>> On May 18, 2014, at 6:13 PM, Ralph Goers <[email protected]> wrote:
>> 
>>> OK - I was able to log in and am running a build.
>>> 
>>> Ralph
>>> 
>>> On May 18, 2014, at 4:24 PM, Matt Sicker <[email protected]> wrote:
>>> 
>>>> I meant to say that while I can log in to Jenkins (used LDAP, wfm), I 
>>>> can't do anything with my account.
>>>> 
>>>> 
>>>> On 18 May 2014 17:42, Ralph Goers <[email protected]> wrote:
>>>> Well rats. I seem to have forgotten my password for Jenkins. It doesn’t 
>>>> seem like it uses the ASF ldap.
>>>> 
>>>> Ralph
>>>> 
>>>> On May 18, 2014, at 2:55 PM, Matt Sicker <[email protected]> wrote:
>>>> 
>>>>> I'm working with Gavin at INFRA right now to see if we can get buildbot 
>>>>> (ci.apache.org) to work properly with log4j. See here:
>>>>> http://ci.apache.org/builders/log4j2-nightly/
>>>>> 
>>>>> Though it might be easier to get working in Jenkins, but I don't have 
>>>>> access to that. I also tried requesting TeamCity or Bamboo, but infra 
>>>>> doesn't want to add yet another CI server (I don't blame them).
>>>>> 
>>>>> 
>>>>> On 18 May 2014 15:47, Christian Grobmeier <[email protected]> wrote:
>>>>> Not related to this problem, but don't we have a CI in place?
>>>>> If not, we should consider to get some help rom Jenkins.
>>>>> 
>>>>> 
>>>>> On 18 May 2014, at 7:36, Ralph Goers wrote:
>>>>> 
>>>>> in some circumstances ThrowableProxy was setting the suppressed proxy to 
>>>>> an empty list. In another case it was setting it to null.  I changed that 
>>>>> case to set it to an empty list to fix ThrowableProxyTest
>>>>> JSONLayoutTest and XMLLayoutTest were also failing because they were 
>>>>> checking for a suppressed exception. However, Throwables.addSuppressed is 
>>>>> a noon on Java6 so no suppressed exceptions were being added.  I made the 
>>>>> check conditional on getSuppressed being present.
>>>>> 
>>>>> Ralph
>>>>> 
>>>>> On May 17, 2014, at 9:50 PM, Ralph Goers <[email protected]> 
>>>>> wrote:
>>>>> 
>>>>> I’ve found the problem. It should be failing for everyone. After I verify 
>>>>> the fix I will check it in.
>>>>> 
>>>>> Ralph
>>>>> 
>>>>> On May 17, 2014, at 8:42 PM, Matt Sicker <[email protected]> wrote:
>>>>> 
>>>>> But I can confirm the same five tests fail for me, too, on JDK6.
>>>>> 
>>>>> 
>>>>> On 17 May 2014 22:35, Matt Sicker <[email protected]> wrote:
>>>>> Those error messages are some of the most unhelpful test failures I've 
>>>>> seen in a long time!
>>>>> 
>>>>> 
>>>>> On 17 May 2014 21:42, Ralph Goers <[email protected]> wrote:
>>>>> After running in the debugger I am guessing that this is failing because 
>>>>> I am using Java 6 to compile and test.  this.suppressedProxies is null 
>>>>> while other.suppressedProxies is not. SuppressedExceptions don’t exist in 
>>>>> Java 6 so I’m not sure why there would be any suppressed proxies.
>>>>> 
>>>>> Ralph
>>>>> 
>>>>> On May 17, 2014, at 7:31 PM, Ralph Goers <[email protected]> 
>>>>> wrote:
>>>>> 
>>>>> I just did a clean checkout and log4j-core fails with the following unit 
>>>>> test failures on my machine.
>>>>> 
>>>>> RollingAppenderTimeTest.testAppender:76 No compressed files found
>>>>> ThrowableProxyTest.testJsonIoContainer:52 expected: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> test> but was: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> test>
>>>>> JSONLayoutTest.testLocationOnCompactOnMdcOn:269->testAllFeatures:116 
>>>>> expected: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> testIOEx> but was: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> testIOEx>
>>>>> JSONLayoutTest.testLocationOffCompactOffMdcOff:264->testAllFeatures:116 
>>>>> expected: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> testIOEx> but was: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> testIOEx>
>>>>> XMLLayoutTest.testLocationOnCompactOnMdcOn:271->testAllFeatures:131 
>>>>> expected: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> testIOEx> but was: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> testIOEx>
>>>>> XMLLayoutTest.testLocationOffCompactOffMdcOff:266->testAllFeatures:131 
>>>>> expected: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> testIOEx> but was: 
>>>>> org.apache.logging.log4j.core.impl.ThrowableProxy<java.io.IOException: 
>>>>> testIOEx>
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Matt Sicker <[email protected]>
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Matt Sicker <[email protected]>
>>>>> 
>>>>> 
>>>>> 
>>>>> ---
>>>>> http://www.grobmeier.de
>>>>> The Zen Programmer: http://bit.ly/12lC6DL
>>>>> @grobmeier
>>>>> GPG: 0xA5CC90DB
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Matt Sicker <[email protected]>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Matt Sicker <[email protected]>
>>> 
>> 
> 

Reply via email to