Github user bschuchardt commented on the issue:

    https://github.com/apache/geode/pull/474
  
    Masaki, this change set is breaking unit tests because the new XSD 
attribute is being put into XML files generated for older versions.  
CacheXml80DUnitTest, for instance, is breaking.  l80Please run the precheckin 
target before posting a fix and ensure that you're not breaking anything.  
Thanks
    
    You should also add a test case in CacheXmlGeode10DUnitTest for the new 
attribute.
    
    org.apache.geode.cache30.CacheXml80DUnitTest > testDefaultConnectionPool 
FAILED
        org.apache.geode.cache.CacheXmlException: While reading Cache XML 
file:/export/india2/users/bschuchardt/devel/gfdev/open/geode-core/build/distributedTest/XML_8_0/CacheXml80DUnitTest_testDefaultConnectionPool.xml.
 Error while parsing XML, caused by org.xml.sax.SAXParseException; lineNumber: 
4; columnNumber: 528; Attribute "socket-connect-timeout" must be declared for 
element type "pool".
    
            org.xml.sax.SAXParseException; lineNumber: 4; columnNumber: 528; 
Attribute "socket-connect-timeout" must be declared for element type "pool".
    
        java.lang.AssertionError: Suspicious strings were written to the log 
during this run.
        Fix the strings or use IgnoredException.addIgnoredException to ignore.
        -----------------------------------------------------------------------
        Found suspect string in log4j at line 91
    
        [error 2017/05/10 12:12:11.923 PDT <Test worker> tid=0x13] While 
reading Cache XML 
file:/export/india2/users/bschuchardt/devel/gfdev/open/geode-core/build/distributedTest/XML_8_0/CacheXml80DUnitTest_testDefaultConnectionPool.xml.
 Error while parsing XML



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to