Hi,
On Fri, Mar 27, 2009 at 6:44 AM, Jim White wrote:
> I get the following test failures with the trunk (r758703) :
>
> Results :
> Failed tests:
> testRemoveAce(org.apache.sling.launchpad.webapp.integrationtest.accessManager.RemoveAcesTest)
&
On Fri, Mar 27, 2009 at 10:27 PM, Michael Groh
wrote:
> Hi,
> I just built the trunk on a mac with no test failures, with the following
> settings:
>
> $mvn -version
> Maven version: 2.0.9
> Java version: 1.6.0_07
> OS name: "mac os x" version: "10.5.6&qu
t the same
errors.
Jim
Eric Norman wrote:
Interesting. I think that JDK 1.5 is fine, that is what I have been using.
Maybe it isn't related to the memory settings in your case. I'm curious
about the details of the test failures.
Could you send me the reports for the unit tests t
Interesting. I think that JDK 1.5 is fine, that is what I have been using.
Maybe it isn't related to the memory settings in your case. I'm curious
about the details of the test failures.
Could you send me the reports for the unit tests that are failing?
Specifically these fi
of Mac, those of us without Core 2 Duo can't get
JDK 1.6 (from Apple anyhow).
Jim
Michael Groh wrote:
Hi,
I just built the trunk on a mac with no test failures, with the
following settings:
$mvn -version
Maven version: 2.0.9
Java version: 1.6.0_07
OS name: "mac os x" vers
Hi,
I just built the trunk on a mac with no test failures, with the
following settings:
$mvn -version
Maven version: 2.0.9
Java version: 1.6.0_07
OS name: "mac os x" version: "10.5.6" arch: "x86_64" Family: "mac"
$export MAVEN_OPTS="-Xmx512M"
est)
Tests run: 239, Failures: 4, Errors: 0, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
----
[INFO] There are test failures.
Please refer to
/Users/jim/Projects/Apache/sling-trunk/launchpad/testing/
ion: 1.5.0_17
OS name: "linux" version: "2.6.27-11-generic" arch: "i386" Family: "unix"
On Thu, Mar 26, 2009 at 9:44 PM, Jim White wrote:
> I get the following test failures with the trunk (r758703) :
>
I get the following test failures with the trunk (r758703) :
Results :
Failed tests:
testRemoveAce(org.apache.sling.launchpad.webapp.integrationtest.accessManager.RemoveAcesTest)
testRemoveAces(org.apache.sling.launchpad.webapp.integrationtest.accessManager.RemoveAcesTest
ok, so for now, I just switch them off, while I try to fix them
Regards
Felix
On Wed, Jan 21, 2009 at 3:53 PM, Bertrand Delacretaz wrote:
> On Wed, Jan 21, 2009 at 3:49 PM, Felix Meschberger
> wrote:
> > ...How about this: We integrate the JCRInstall integration tests with the
> > main integra
On Wed, Jan 21, 2009 at 3:49 PM, Felix Meschberger wrote:
> ...How about this: We integrate the JCRInstall integration tests with the
> main integration tests by means of a build profile. You may then switch
> on or off this profile to run the integration tests with or without
> JCRInstall
Th
Hi,
Bertrand Delacretaz schrieb:
> On Wed, Jan 21, 2009 at 3:22 PM, Felix Meschberger wrote:
>> ...ok, how about removing jcr install from the default build ? Like for
>> example create a new inactive-by-default profile for jcrinstall ?...
>
> I'd be ok with that if we have a continuous integrat
On Wed, Jan 21, 2009 at 3:22 PM, Felix Meschberger wrote:
> ...ok, how about removing jcr install from the default build ? Like for
> example create a new inactive-by-default profile for jcrinstall ?...
I'd be ok with that if we have a continuous integration setup where
those jcrinstall tests run
Hi,
Bertrand Delacretaz schrieb:
> On Wed, Jan 21, 2009 at 3:02 PM, Felix Meschberger wrote:
>> ...I have a question anyway: Shoulnd't the jcrinstall install integration
>> tests not be integrated with the launchpad integration tests anyway ?...
>
> I created a separate testing module for jcrins
On Wed, Jan 21, 2009 at 3:02 PM, Felix Meschberger wrote:
> ...I have a question anyway: Shoulnd't the jcrinstall install integration
> tests not be integrated with the launchpad integration tests anyway ?...
I created a separate testing module for jcrinstall as we were
experiencing concurrency i
Hi,
Hmm, looks like I forgot to migrate the jcrinstall integration test
module to the new launchpad.
I have a question anyway: Shoulnd't the jcrinstall install integration
tests not be integrated with the launchpad integration tests anyway ?
Regards
Felix
Andreas Hartmann schrieb:
> Hi Sling de
Hi Sling devs,
I just did a fresh checkout of the trunk (Mac OS X, Java 1.5.0_16).
The command
mvn -s /dev/null clean install
resulted in
Failed tests:
testWebServerRoot(org.apache.sling.jcr.jcrinstall.integrationtest.HttpPingTest)
test404(org.apache.sling.jcr.jcrinstall.integrationtest.Htt
d after I deleted the /.m2/repository...
Same here, I had to delete the local repository on a machine where I hadn't run
the Sling build for a few days. Revision 734151 builds fine after this.
> Build fails due to multiple test failures. (Could not i
[
https://issues.apache.org/jira/browse/SLING-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pontus Amberg closed SLING-824.
---
> Build fails due to multiple test failures. (Could not initialize cl
problems was probably caused by old Sling stuff in the repository.
> Build fails due to multiple test failures. (Could not initialize class
> org.apache.commons.httpclient.Http
extensions/jcrinstall/pom.xml the build fails again with 208
errors in org.apache.sling.launchpad.webapp.integrationtest. I haven't check
all the new failed test but there seems to be problems with
org.apache.commons.httpclient.HttpClient again.
> Build fails due to multiple test failures. (C
fails due to multiple test failures. (Could not initialize class
> org.apache.commons.httpclient.HttpClient)
>
>
> Key: SLING-824
> URL: htt
when unfolding the parent pom dependencies for
SLING-811.
The httpclient dependency must be compile scoped and not test scoped for the
tests to be runnable.
Fixed in Rev. 733351.
If this also solves the issue on your platform, please close this issue. Thanks.
> Build fails due to multiple t
[
https://issues.apache.org/jira/browse/SLING-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-824:
Affects Version/s: JCR Install 2.0.4
> Build fails due to multiple test failures. (Co
[
https://issues.apache.org/jira/browse/SLING-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-824:
---
Assignee: Felix Meschberger
> Build fails due to multiple test failures. (Could
false
testing
> Build fails due to multiple test failures. (Could not initialize class
> org.apache.commons.httpclie
ild fails due to multiple test failures. (Could not initialize class
> org.apache.commons.httpclient.HttpClient)
>
>
> Key: SLING-824
>
ils due to multiple test failures. (Could not initialize class
> org.apache.commons.httpclient.HttpClient)
>
>
> Key: SLING-824
> URL: https:/
> Build fails due to multiple test failures. (Could not initialize class
> org.apache.commons.httpclient.HttpClient)
>
>
> Key: SLING-824
>
> Build fails due to multiple test failures. (Could not initialize class
> org.apache.commons.httpclient.HttpClient)
>
>
> Key: SLING-824
>
Build fails due to multiple test failures. (Could not initialize class
org.apache.commons.httpclient.HttpClient)
Key: SLING-824
URL: https
Right. That works. Thanks.
On 16.05.2008 12:15:29 Felix Meschberger wrote:
> Yes, sorry, this is a bit tricky
>
> After the update and "mvn install" of the engine module (which contains
> the fix for this) you have to "mvn clean install" the launchpad/app
> module and then you should be able
Yes, sorry, this is a bit tricky
After the update and "mvn install" of the engine module (which contains
the fix for this) you have to "mvn clean install" the launchpad/app
module and then you should be able to build the web app incl. tests
properly.
Regards
Felix
Am Freitag, den 16.05.2008
These tests run through now. Thanks. Now, I have another test failure in
the test introduced by http://svn.apache.org/viewvc?rev=656974&view=rev
(SLING457Test, method testCallHtml)
---
Test set: org.apache.sling.launchpad.
34 matches
Mail list logo
