Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
Gump is failing this because it is using the trunk version of junit 4. There was a bug fix that now causes TemporaryFile's newFile method to throw an exception if the file previously existed. Commons Config was perfectly happy with having the file previously exist. So I either have to file a bug against their fix or we need to recode the tests to accommodate for this. Ralph On Apr 16, 2012, at 11:09 PM, Gump wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 12 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 46 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.03 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.configuration.reloading.TestManagedReloadingStrategy Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.configuration.reloading.TestVFSFileChangedReloadingStrategy Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.018 sec Running org.apache.commons.configuration.reloading.TestFileChangedReloadingStrategy Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.028 sec Results : Tests in error: testReloading(org.apache.commons.configuration.TestCombinedConfiguration): a file with the name 'reload.xml' already exists in the test folder testReloadWithSubNodeConfig(org.apache.commons.configuration.TestCombinedConfiguration): a file with the name 'reload.xml' already exists in the test folder testReloadingNestedCC(org.apache.commons.configuration.TestCombinedConfiguration): a file with the name 'reload.xml' already exists in the test folder testReloadingSubnodeConfig(org.apache.commons.configuration.TestCombinedConfiguration): a file with the name 'reload.xml' already exists in the test folder Tests
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
On 17 April 2012 07:34, Ralph Goers ralph.go...@dslextreme.com wrote: Gump is failing this because it is using the trunk version of junit 4. There was a bug fix that now causes TemporaryFile's newFile method to throw an exception if the file previously existed. Commons Config was perfectly happy with having the file previously exist. So I either have to file a bug against their fix or we need to recode the tests to accommodate for this. Seems to me that it is a config test bug if the temporary file exists. Either the test code should not be using newFile(), or it should use a different name, or the test code needs to ensure that other test cases don't leave crap behind. Ralph On Apr 16, 2012, at 11:09 PM, Gump wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 12 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 46 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.03 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.configuration.reloading.TestManagedReloadingStrategy Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.configuration.reloading.TestVFSFileChangedReloadingStrategy Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.018 sec Running org.apache.commons.configuration.reloading.TestFileChangedReloadingStrategy Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.028 sec Results : Tests in error: testReloading(org.apache.commons.configuration.TestCombinedConfiguration): a file with the name 'reload.xml' already exists in the test folder testReloadWithSubNodeConfig(org.apache.commons.configuration.TestCombinedConfiguration): a file with the name 'reload.xml' already exists in the test folder
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
All the tests that fail are testing file reloading, meaning the file is created at the beginning of the test and is modified at least once during the test. I've modified the test so that it doesn't use newFile. Ralph On Apr 17, 2012, at 4:02 AM, sebb wrote: On 17 April 2012 07:34, Ralph Goers ralph.go...@dslextreme.com wrote: Gump is failing this because it is using the trunk version of junit 4. There was a bug fix that now causes TemporaryFile's newFile method to throw an exception if the file previously existed. Commons Config was perfectly happy with having the file previously exist. So I either have to file a bug against their fix or we need to recode the tests to accommodate for this. Seems to me that it is a config test bug if the temporary file exists. Either the test code should not be using newFile(), or it should use a different name, or the test code needs to ensure that other test cases don't leave crap behind. Ralph On Apr 16, 2012, at 11:09 PM, Gump wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 12 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 46 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.03 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.configuration.reloading.TestManagedReloadingStrategy Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.configuration.reloading.TestVFSFileChangedReloadingStrategy Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.018 sec Running org.apache.commons.configuration.reloading.TestFileChangedReloadingStrategy Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.028 sec Results : Tests in error:
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
On 17 April 2012 13:22, Ralph Goers ralph.go...@dslextreme.com wrote: All the tests that fail are testing file reloading, meaning the file is created at the beginning of the test and is modified at least once during the test. I've modified the test so that it doesn't use newFile. OK, that makes sense. Ralph On Apr 17, 2012, at 4:02 AM, sebb wrote: On 17 April 2012 07:34, Ralph Goers ralph.go...@dslextreme.com wrote: Gump is failing this because it is using the trunk version of junit 4. There was a bug fix that now causes TemporaryFile's newFile method to throw an exception if the file previously existed. Commons Config was perfectly happy with having the file previously exist. So I either have to file a bug against their fix or we need to recode the tests to accommodate for this. Seems to me that it is a config test bug if the temporary file exists. Either the test code should not be using newFile(), or it should use a different name, or the test code needs to ensure that other test cases don't leave crap behind. Ralph On Apr 16, 2012, at 11:09 PM, Gump wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 12 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 46 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.03 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.configuration.reloading.TestManagedReloadingStrategy Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.configuration.reloading.TestVFSFileChangedReloadingStrategy Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.018 sec Running org.apache.commons.configuration.reloading.TestFileChangedReloadingStrategy Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.028
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
I've looked at this and I simply think testValidation and testValidation2 are incorrect. I believe their purpose is to test schema validation. If that failed they would throw an exception. The two asserts after reading the configuration don't actually validate anything those tests are doing. They work if testSystemProperties() runs before them but will fail if they run before it does. Since the order of tests isn't guaranteed this is just accidental. My guess is I copied testSystemProperties when I created testValidation and testValidation2 and didn't think about that. Ralph On Mar 31, 2012, at 12:03 PM, Oliver Heger wrote: I had a look at this issue, but could not come to a conclusion. A test case for TestVFSConfigurationBuilder is failing. At first I suspected a recent change in [vfs] would cause the problem. However, I could locally build [configuration] with the recent [vfs] snapshot version without any problems. So I assume the breaking change is somewhere deeper in the dependency chain. This would also explain why the Gump build for [vfs] is failing, too. Does anybody have an idea? BTW, there are currently a bunch of failing Gump builds. Oliver Am 31.03.2012 06:13, schrieb Gump: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 77 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 46 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.TestHierarchicalConfigurationXMLReader Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec Running org.apache.commons.configuration.TestNullCompositeConfiguration Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.133 sec Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.691 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
On 1 April 2012 06:23, Stefan Bodewig bode...@apache.org wrote: On 2012-04-01, Ralph Goers wrote: From the vfs2 log it looks like it is running into a binary incompatibility with SLF4J. vfs2 is specifying SLF4J 1.5.5 but mvn dependency:tree is showing me that Jackrabbit is referencing jcl-over-slf4j and is using 1.5.3. I've added that to the vfs2 pom in hopes that Gump will honor it. It won't. Gump puts a proxy between mvn and the repo and always serves the latest version by artifactId/groupId coordinates. If a project breaks backwards compatibility without changing either of them Gump doesn't provide any proper way to deal with it. Nor should it - AFAICT that is a fundamental error by the project; it should change Maven coords and package name when breaking compat. If it is trying to use the latest SLF4J then this can't be fixed as 1.6.0 introduced a breakage with LocationAwareLogger (at my request by the way). vfs2 doesn't actually use SLF4J - Jackrabbit does. Given VFS is not the only project suffering from this and the slf4j project never asked for being included in Gump it might be the best idea to stop building slf4j in Gump and give the remaining projects the version they ask for. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
On 1 April 2012 06:18, Stefan Bodewig bode...@apache.org wrote: On 2012-04-01, Ralph Goers wrote: I have real problems with Gump. I find it very difficult to determine what the problem actually is much less diagnose it. Other than that I know it is supposed to be using the latest source in trunk it is tough to figure out how to reproduce a problem as it means manually going to all the dependencies and building them from trunk and then modifying poms to use them. Agreed, but I wouldn't know of a simpler way to do it. In theory you could do a bisect on all changes of all dependencies until you identify the change that introduced a breakage on the Gump side, but that's non-trivial and will likely never happen given the limited development resources at Gump. Of course the process is easier for projects with a small transitive hull of dependencies 8-) I know its purpose is to try to catch errors early, but it looks to me like people are just giving up trying to fix them. Frankly, I think the only reason people do tis to try to stop the emails. I think you are correct. Many projects have stopped seeing value in Gump and only view it as a nuisance (or ignore it), I don't know what to do about it either. Or educate people on why the Gump errors can be useful? And how to debug them... It recently found a bug in a Lang test case (different order of test execution exposed cleanup failures). And this particular error seems to be the same cause (see else-thread). Another way to get rid of the emails is to remove the nag element from the Gump descriptor. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
I had a look at this issue, but could not come to a conclusion. A test case for TestVFSConfigurationBuilder is failing. At first I suspected a recent change in [vfs] would cause the problem. However, I could locally build [configuration] with the recent [vfs] snapshot version without any problems. So I assume the breaking change is somewhere deeper in the dependency chain. This would also explain why the Gump build for [vfs] is failing, too. Does anybody have an idea? BTW, there are currently a bunch of failing Gump builds. Oliver Am 31.03.2012 06:13, schrieb Gump: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 77 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 46 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.TestHierarchicalConfigurationXMLReader Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec Running org.apache.commons.configuration.TestNullCompositeConfiguration Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.133 sec Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.691 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.configuration.reloading.TestManagedReloadingStrategy Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.configuration.reloading.TestVFSFileChangedReloadingStrategy Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.011 sec Running org.apache.commons.configuration.reloading.TestFileChangedReloadingStrategy Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.019 sec Results : Failed tests: testValidation2(org.apache.commons.configuration.TestVFSConfigurationBuilder): The test key was not located Tests run: 1595, Failures: 1, Errors: 0, Skipped: 0 [INFO] [ERROR]
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
I have real problems with Gump. I find it very difficult to determine what the problem actually is much less diagnose it. Other than that I know it is supposed to be using the latest source in trunk it is tough to figure out how to reproduce a problem as it means manually going to all the dependencies and building them from trunk and then modifying poms to use them. I know its purpose is to try to catch errors early, but it looks to me like people are just giving up trying to fix them. Frankly, I think the only reason people do tis to try to stop the emails. Ralph On Mar 31, 2012, at 12:03 PM, Oliver Heger wrote: I had a look at this issue, but could not come to a conclusion. A test case for TestVFSConfigurationBuilder is failing. At first I suspected a recent change in [vfs] would cause the problem. However, I could locally build [configuration] with the recent [vfs] snapshot version without any problems. So I assume the breaking change is somewhere deeper in the dependency chain. This would also explain why the Gump build for [vfs] is failing, too. Does anybody have an idea? BTW, there are currently a bunch of failing Gump builds. Oliver Am 31.03.2012 06:13, schrieb Gump: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 77 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 46 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.TestHierarchicalConfigurationXMLReader Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec Running org.apache.commons.configuration.TestNullCompositeConfiguration Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.133 sec Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.691 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
From the vfs2 log it looks like it is running into a binary incompatibility with SLF4J. vfs2 is specifying SLF4J 1.5.5 but mvn dependency:tree is showing me that Jackrabbit is referencing jcl-over-slf4j and is using 1.5.3. I've added that to the vfs2 pom in hopes that Gump will honor it. If it is trying to use the latest SLF4J then this can't be fixed as 1.6.0 introduced a breakage with LocationAwareLogger (at my request by the way). vfs2 doesn't actually use SLF4J - Jackrabbit does. Ralph On Mar 31, 2012, at 12:03 PM, Oliver Heger wrote: I had a look at this issue, but could not come to a conclusion. A test case for TestVFSConfigurationBuilder is failing. At first I suspected a recent change in [vfs] would cause the problem. However, I could locally build [configuration] with the recent [vfs] snapshot version without any problems. So I assume the breaking change is somewhere deeper in the dependency chain. This would also explain why the Gump build for [vfs] is failing, too. Does anybody have an idea? BTW, there are currently a bunch of failing Gump builds. Oliver Am 31.03.2012 06:13, schrieb Gump: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 77 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-configuration-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -WARNING- Overriding Maven settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml] -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/configuration/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html Work Name: build_apache-commons_commons-configuration-test (Type: Build) Work ended in a state of : Failed Elapsed: 1 min 46 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/configuration] M2_HOME: /opt/maven2 - Running org.apache.commons.configuration.TestHierarchicalConfigurationXMLReader Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec Running org.apache.commons.configuration.TestNullCompositeConfiguration Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.133 sec Running org.apache.commons.configuration.interpol.TestConfigurationInterpolator Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec Running org.apache.commons.configuration.interpol.TestEnvironmentLookup Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.configuration.interpol.TestExprLookup Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.interpol.TestConstantLookup Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.configuration.TestPropertiesConfigurationLayout Tests run: 38, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 sec Running org.apache.commons.configuration.TestConfigurationConverter Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.commons.configuration.TestFileConfiguration Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.691 sec Running org.apache.commons.configuration.TestPatternSubtreeConfiguration Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running org.apache.commons.configuration.TestPropertyConverter Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec Running org.apache.commons.configuration.TestConfigurationMap Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.configuration.reloading.TestManagedReloadingStrategy Tests run: 1, Failures: 0, Errors: 0,
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
On 2012-04-01, Ralph Goers wrote: I have real problems with Gump. I find it very difficult to determine what the problem actually is much less diagnose it. Other than that I know it is supposed to be using the latest source in trunk it is tough to figure out how to reproduce a problem as it means manually going to all the dependencies and building them from trunk and then modifying poms to use them. Agreed, but I wouldn't know of a simpler way to do it. In theory you could do a bisect on all changes of all dependencies until you identify the change that introduced a breakage on the Gump side, but that's non-trivial and will likely never happen given the limited development resources at Gump. Of course the process is easier for projects with a small transitive hull of dependencies 8-) I know its purpose is to try to catch errors early, but it looks to me like people are just giving up trying to fix them. Frankly, I think the only reason people do tis to try to stop the emails. I think you are correct. Many projects have stopped seeing value in Gump and only view it as a nuisance (or ignore it), I don't know what to do about it either. Another way to get rid of the emails is to remove the nag element from the Gump descriptor. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
On 2012-04-01, Ralph Goers wrote: From the vfs2 log it looks like it is running into a binary incompatibility with SLF4J. vfs2 is specifying SLF4J 1.5.5 but mvn dependency:tree is showing me that Jackrabbit is referencing jcl-over-slf4j and is using 1.5.3. I've added that to the vfs2 pom in hopes that Gump will honor it. It won't. Gump puts a proxy between mvn and the repo and always serves the latest version by artifactId/groupId coordinates. If a project breaks backwards compatibility without changing either of them Gump doesn't provide any proper way to deal with it. If it is trying to use the latest SLF4J then this can't be fixed as 1.6.0 introduced a breakage with LocationAwareLogger (at my request by the way). vfs2 doesn't actually use SLF4J - Jackrabbit does. Given VFS is not the only project suffering from this and the slf4j project never asked for being included in Gump it might be the best idea to stop building slf4j in Gump and give the remaining projects the version they ask for. Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [GUMP@vmgump]: Project commons-configuration-test (in module apache-commons) failed
On Mar 31, 2012, at 10:23 PM, Stefan Bodewig wrote: On 2012-04-01, Ralph Goers wrote: From the vfs2 log it looks like it is running into a binary incompatibility with SLF4J. vfs2 is specifying SLF4J 1.5.5 but mvn dependency:tree is showing me that Jackrabbit is referencing jcl-over-slf4j and is using 1.5.3. I've added that to the vfs2 pom in hopes that Gump will honor it. It won't. Gump puts a proxy between mvn and the repo and always serves the latest version by artifactId/groupId coordinates. If a project breaks backwards compatibility without changing either of them Gump doesn't provide any proper way to deal with it. If it is trying to use the latest SLF4J then this can't be fixed as 1.6.0 introduced a breakage with LocationAwareLogger (at my request by the way). vfs2 doesn't actually use SLF4J - Jackrabbit does. Given VFS is not the only project suffering from this and the slf4j project never asked for being included in Gump it might be the best idea to stop building slf4j in Gump and give the remaining projects the version they ask for. Actually, I think there is something else wrong. I just looked at the last Gump run for VFS2 and it is complaining that there are multiple SLF4J bindings. The first is coming from slf4j-log4j12 which I believe binds SLF4j to Log4j. The second is coming from Jackrabbit itself. I did a jar -tf on jackrabbit-standalone-1.6.5.jar and it includes a whole pile of classes that aren't from Jackrabbit. I believe Gary added this to be able to test WebDAV directly during the build. I have no idea why we don't encounter any errors during the normal build as -X shows both jars are present on the test class path. Ralph - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
