Test Failure:mixin nodetype mix:simpleVersionable is missing

Hi,

I am attempting to build the C client on debian lenny.

autoconf, configure, make and make install all appear to work cleanly.

I ran:

autoreconf -if
./configure
make
make install
make run-check

However, the unit tests fail:

$ make run-check
make  zktest-st zktest-mt
make[1]: Entering directory `/home/martin/zookeeper-3.3.1/src/c'
make[1]: `zktest-st' is up to date.
make[1]: `zktest-mt' is up to date.
make[1]: Leaving directory `/home/martin/zookeeper-3.3.1/src/c'
./zktest-st
./tests/zkServer.sh: line 52: kill: (17711) - No such process
 ZooKeeper server startedRunning
Zookeeper_operations::testPing : elapsed 1 : OK
Zookeeper_operations::testTimeoutCausedByWatches1 : elapsed 0 : OK
Zookeeper_operations::testTimeoutCausedByWatches2 : elapsed 0 : OK
Zookeeper_operations::testOperationsAndDisconnectConcurrently1 : elapsed 2
:
OK
Zookeeper_operations::testOperationsAndDisconnectConcurrently2 : elapsed 0
:
OK
Zookeeper_operations::testConcurrentOperations1 : elapsed 206 : OK
Zookeeper_init::testBasic : elapsed 0 : OK
Zookeeper_init::testAddressResolution : elapsed 0 : OK
Zookeeper_init::testMultipleAddressResolution : elapsed 0 : OK
Zookeeper_init::testNullAddressString : elapsed 0 : OK
Zookeeper_init::testEmptyAddressString : elapsed 0 : OK
Zookeeper_init::testOneSpaceAddressString : elapsed 0 : OK
Zookeeper_init::testTwoSpacesAddressString : elapsed 0 : OK
Zookeeper_init::testInvalidAddressString1 : elapsed 0 : OK
Zookeeper_init::testInvalidAddressString2 : elapsed 2 : OK
Zookeeper_init::testNonexistentHost : elapsed 108 : OK
Zookeeper_init::testOutOfMemory_init : elapsed 0 : OK
Zookeeper_init::testOutOfMemory_getaddrs1 : elapsed 0 : OK
Zookeeper_init::testOutOfMemory_getaddrs2 : elapsed 0 : OK
Zookeeper_init::testPermuteAddrsList : elapsed 0 : OK
Zookeeper_close::testCloseUnconnected : elapsed 0 : OK
Zookeeper_close::testCloseUnconnected1 : elapsed 0 : OK
Zookeeper_close::testCloseConnected1 : elapsed 0 : OK
Zookeeper_close::testCloseFromWatcher1 : elapsed 0 : OK
Zookeeper_simpleSystem::testAsyncWatcherAutoResetterminate called after
throwing an instance of 'CppUnit::Exception'
  what():  equality assertion failed
- Expected: -101
- Actual  : -4

make: *** [run-check] Aborted

This appears to come from tests/TestClient.cc - but beyond that, it is
hard
to identify which equality assertion failed.

Help !

regards,
Martin

Test failure in ShowArtifactActionTest for certain locales

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Pierre-Arnaud Marcelot resolved DIRSERVER-1456.

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Mike Matrigali resolved DERBY-4132.

hi all,


from what I checked in the source of version 2.1.0, jackrabbit still
doesn't
create the jcr:etag property.
is there a version planned where this feature is implemented?


thanks all for your help.




best regards,

bruno coelho

Hi,
I have just updated my dependencies to match trunk head (sorry been
fighting fires so needed to be behind trunk), and a lots of the files that
used to load via the content loader wont any more. (property def not found)

Has some thing changed recently that now requires the sling:Resource mixin
on all nodes ?

Ian

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Stefan Guggisberg resolved JCR-2659.

Hi

I'm seeing the following build failure on the 2.2.x branch, in
uncategorized
system tests :

[INFO] org.apache.cxf.wsdl11.WSDLRuntimeException: Fail to create wsdl
definition from :
file:/home/sberyozkin/work/cxf/2.2.x/systests/uncategorized/src/test/resources/wsdl_systest/soap_fault.wsdl
Caused by : WSDLException (at /definitions/types/s:schema):
faultCode=PARSER_ERROR: Problem parsing '
http://schemas.xmlsoap.org/soap/envelope/'.:
org.xml.sax.SAXParseException:
The declaration for the entity "ContentType" must end with '>'.


Is it only me ? Can someone try and build the 2.2.x ?

thanks, Sergey

I am looking at Cassandra 0.6.2's source code, and am unable to figure  
out where, if at all, repartitioning happens in the case of failure.   
The Gossiper's onDead message is ignored. Can someone please clarify  
this for me? 

Hi all,

This test is currently failing in Hudson. Could someone knowledgeable
(Marc?) please have a look?
org.apache.cxf.dosgi.topologymanager.TopologyManagerImportTest.testImportForNewlyAddedRSA

http://hudson.zones.apache.org/hudson...i/172/testReport/

Thanks!

David

Couchers,

I'm trying to replicate a database down to my local workstation, but
the replication seems to fail after a certain point:

$ curl -X POST http://*******:*******@localhost:5984/_replicate -d
'{"source":"http://*******:*******@couch.mydomain.com:5984/backlogger","target":"backlogger","create_target":true}'

{"error":"json_encode","reason":"{bad_term,{couch_rep_reader,'-open_doc_revs/3-fun-1-',\n
                          
[{[{<<\"error\">>,<<\"unauthorized\">>},\n
                             {<<\"reason\">>,\n
        <<\"You are not authorized to access this
db.\">>}]},\n

{http_db,\"http://*******:*******@couch.mydomain.com:5984/backlogger/\",\n
                                     [],[],\n
            [{\"User-Agent\",\"CouchDB/1.0.0\"},\n
                  {\"Accept\",\"application/json\"},\n
                      {\"Accept-Encoding\",\"gzip\"}],\n
                       [],get,nil,\n
   [{response_format,binary},\n
{inactivity_timeout,30000},\n
{max_sessions,10},\n
{max_pipeline_size,10}],\n
10,500,nil}]}}"}

Note that it did create the database locally, and that 130 out of the
137 docs seem to have made it over:

$ curl localhost:5984/backlogger

{"db_name":"backlogger","doc_count":130,"doc_del_count":32,"update_seq":162,"purge_seq":0,"compact_running":false,"disk_size":348249,"instance_start_time":"1279204723544778","disk_format_version":5}

$ curl http://*******:*******@couch.mydomain.com:5984/backlogger

{"db_name":"backlogger","doc_count":137,"doc_del_count":39,"update_seq":402,"purge_seq":0,"compact_running":false,"disk_size":290909,"instance_start_time":"1279204391630006","disk_format_version":5}

I re-ran the replication, and the number of docs locally went up to
135, but it still failed with the same error message. After that,
re-running the replication seemed to cause no further changes to my
local database.

Any ideas how I can complete the replication?

FYI, I'm running 1.0.0 locally and 0.11.0 on the remote server.


Cheers,

Zach

On 22 July 2010 21:15,  <mben### @apache.org> wrote:
 Author: mbenson
 Date: Thu Jul 22 20:15:25 2010
 New Revision: 966839

 URL: http://svn.apache.org/viewvc?rev=966839&view=rev
 Log:
 add new test module to exercise the defaultProxyFactory

 Added:
    commons/proper/proxy/branches/version-2.0-work/test/   (with
props)
    commons/proper/proxy/branches/version-2.0-work/test/pom.xml

Needs svn:eol-style native

    commons/proper/proxy/branches/version-2.0-work/test/src/
    commons/proper/proxy/branches/version-2.0-work/test/src/main/
  
 commons/proper/proxy/branches/version-2.0-work/test/src/main/java/
    commons/proper/proxy/branches/version-2.0-work/test/src/test/
  
 commons/proper/proxy/branches/version-2.0-work/test/src/test/java/
  
 commons/proper/proxy/branches/version-2.0-work/test/src/test/java/org/
  
 commons/proper/proxy/branches/version-2.0-work/test/src/test/java/org/apache/
  
 commons/proper/proxy/branches/version-2.0-work/test/src/test/java/org/apache/commons/
  
 commons/proper/proxy/branches/version-2.0-work/test/src/test/java/org/apache/commons/proxy/
  
 commons/proper/proxy/branches/version-2.0-work/test/src/test/java/org/apache/commons/proxy/DefaultProxyFactoryTest.java

Needs svn:eol-style native

 Modified:
    commons/proper/proxy/branches/version-2.0-work/pom.xml

 Modified: commons/proper/proxy/branches/version-2.0-work/pom.xml
 URL:
http://svn.apache.org/viewvc/commons/...839&view=diff
 

     [
https://issues.apache.org/jira/browse...nels:all-tabpanel
]

Kiran Ayyagari closed DIRSERVER-1480.

Author: markt
Date: Wed Jun  2 11:45:11 2010
New Revision: 950507

URL: http://svn.apache.org/viewvc?rev=950507&view=rev
Log:
Fix Eclipse warnings in the o.a.c.tribes.test package

Modified:
   
tomcat/trunk/test/org/apache/catalina/tribes/test/channel/TestDataIntegrity.java
   
tomcat/trunk/test/org/apache/catalina/tribes/test/channel/TestMulticastPackages.java
   
tomcat/trunk/test/org/apache/catalina/tribes/test/channel/TestRemoteProcessException.java
   
tomcat/trunk/test/org/apache/catalina/tribes/test/channel/TestUdpPackages.java
   
tomcat/trunk/test/org/apache/catalina/tribes/test/io/TestSenderConnections.java
   
tomcat/trunk/test/org/apache/catalina/tribes/test/io/TestSerialization.java

Modified:
tomcat/trunk/test/org/apache/catalina/tribes/test/channel/TestDataIntegrity.java
URL:
http://svn.apache.org/viewvc/tomcat/t...507&view=diff

Hi Michelle,

should these changes go into the api subproject (instead of api2)?
I think having them in api2 does not hurt, so there is no need to 
rollback the checkin. But we need them in api, since api defines the JDO 
3 API classes and interfaces.

Regards Michael


 Author: mcaisse
 Date: Sun Jun 20 02:54:01 2010
 New Revision: 956317

 URL: http://svn.apache.org/viewvc?rev=956317&view=rev
 Log:
 JDO-557 - Tests for api's invocation of getPersistenceManager(Map)
and getPersistenceManager(Map, Map). Also fixed an issue in
JDOConfigTestClassLoader.java.


 Added:
     db/jdo/trunk/api2/test/java/javax/jdo/PMFMapMapTest.java
     db/jdo/trunk/api2/test/java/javax/jdo/PMFProxy.java
     db/jdo/trunk/api2/test/java/javax/jdo/PMFService.java
     db/jdo/trunk/api2/test/schema/jdoconfig/Pmfmapmap01/
     db/jdo/trunk/api2/test/schema/jdoconfig/Pmfmapmap01/META-INF/
    
db/jdo/trunk/api2/test/schema/jdoconfig/Pmfmapmap01/META-INF/jdoconfig.xml
     db/jdo/trunk/api2/test/schema/jdoconfig/Pmfmapmap02/
    
db/jdo/trunk/api2/test/schema/jdoconfig/Pmfmapmap02/propsfile.props
 Modified:
     db/jdo/trunk/api2/   (props changed)
    
db/jdo/trunk/api2/test/java/javax/jdo/JDOConfigTestClassLoader.java

 Propchange: db/jdo/trunk/api2/
 

I wonder why the very clear thing like "zero test failures" always ends up
with test architecture discussion. :-)






On Thu, May 27, 2010 at 5:22 AM, Nathan Beyer <ndbe### @apache.org>
wrote:

 On Wed, May 26, 2010 at 4:59 AM, Mark Hindess
 <mark.hi### @googlemail.com> wrote:
 >
 > In message
<201005250742.### @d06av01.portsmouth.uk.ibm.com>,
 > Mark Hindess writes:
 >>
 >> In message <
 AANLkTikh3nV56QB8HXSXfzLnI9jrtU-C2cRF1s### @mail.gmail.com>,
 >> Nathan Beyer writes:
 >> >
 >> > For future milestone votes, I'd like to propose that we
set the
 >> > expectation of zero test failures. Every time we do a
milestone and I
 >> > run the build and tests I find myself looking at the
test failures
 >> > (there are ALWAYS failures) and ask 'are these
expected'? If the
 >> > failures are expected, they should be excluded and the
tests should
 >> > just pass.
 >> >
 >> > If this proposal is workable, immediately after this
upcoming release,
 >> > all 'expected' failures will be pulled into the
exclusion lists.
 >>
 >> I was thinking this too.  The problem for me is that:
 >>
 >> 1) Our test coverage isn't brilliant so we need a way to
exclude
 >> individual tests not the tests for a whole class.  We have
too many
 >> excluded tests already[0].
 >>
 >> 2) The JDWP test framework seems to pass most of the time on
the 5.0
 >> code base but seems to fail quite often on the 6.0 branch. 
I normally
 >> resort to doing 10 test runs and comparing the results of
all runs. I
 >> typically see every test pass on at least one run.  This
leads me to
 >> believe that the improved jdwp in the 6.0 branch is merely
exposing race
 >> conditions in the test framework.  It would be great to fix
the test
 >> framework so that these are avoided.  If we tried to exclude
tests that
 >> fail regularly on java6 jdwp we would probably end up
removing most of
 >> the tests. ;-(
 >>
 >> I think solving 1 is really a pre-requisite to moving
forward with your
 >> (excellent) goal.  We should make that a priority after this
release.  I
 >> don't care if the solution is something fancy with junit 4
annotations
 >> or something simple like adding:
 >>
 >>   if (Support_Excludes.isExcluded()) {
 >>     return;
 >>   }
 >>
 >> to problematic tests where the support class just looks up
the
 >> class/method name of the caller in the exclude lists.  (I
actually
 >> quite like the idea of doing the exclude list processing
lazily at
 >> run time rather than generating the list with ant.)
 >
 > Last night I decided to try to implement this simple exclude
list
 > mechanism in my build-improvement branch.  I've checked in my
changes at
 >

https://svn.apache.org/repos/asf/harm...anches/mr### @948377

 I don't want to be rude, but ... I brought this up a few months back
 and the response I got was less than overwhelming. I stopped my work.
 How is this different?


http://harmony.markmail.org/message/4...=junit annotation

 >
 > I've automatically added isExcluded() checks to all the test
methods
 > in previously excluded tests (though this was automated and more
 > complicated than you might think, and definitely not 100%
accurate
 > but should be close enough).  The next job would be to
remove/move
 > the isExcluded() checks to be as fine-grained as possible so as
just
 > to exclude the failing tests (or individual asserts).  As I
commented
 > previously many of the excludes probably just need to be removed
 > completely.
 >
 > New excludes can be added as before by adding tests names to the
lists
 > but you also need to add an appropriate isExcluded()-if check to
the
 > test code as well.  Hopefully this will maximize coverage will
still
 > allowing us to have only passing tests running by default.
 >
 > If different exclude conditions apply to different platforms you
can
 > use:
 >
 >  package.class#methodname
 >  package.class+arbitrary_tag
 >  package.class#methodname+arbitrary_tag
 >  arbitrary_tag
 >
 > to exclude tests - though I'd avoid the final one unless it is
something
 > really broad like a VM not supporting concurrent (like the IBM
v4 VMEs).
 >
 > To see what is happening, you can run the tests with:
 >
 >  -Dhy.test.vmargs=-Dhy.excludes.verbose=true
 >
 > (though this is too verbose I might make the load method less
verbose
 > or use a hy.excludes.debug=true flag for that output).
 >
 > To ignore excludes and run all tests use:
 >
 >  -Dhy.test.vmargs=-Dhy.excludes.ignore=true
 >
 > Rather than using test-jre-vm-info in ant the vm name for the
exclude
 > file selection is a trivial guess based on system properties. If
you
 > are using a custom vm and exclude lists then you can use:
 >
 >  -Dhy.test.vmargs=-Dhy.excludes.vm=myvm
 >
 > to set it explicitly.
 >
 > I'm tempted to do away with the isExcluded() checks/lists are
replace
 > them with more readable:
 >
 >  if (Support_Excludes.isRI()) {
 >
 > or:
 >
 >  if (Support_Excludes.isLinux() &&
Support_Excludes.is64bit()) {
 >
 > etc.  To make the Excludes more self-contained but that requires
 > looking at the excluded tests in more detail to understand the
 > requirements better and as I said I wanted to make this a simple
 > step from what we had today.
 >
 > I'd like to merge this to trunk/java6 after the code freeze but
I'd
 > like some feedback first.  I don't necessarily see this as a
final
 > solution but I just wanted to do something since this topic has
been
 > discussed for far to long and I wanted something that we could
move to
 > from where we are today without to much effort.  On the other
hand,
 > I'm not convinced that annotations are a good solution either
since
 > they don't give you fine-grained control so every distinction
has to be
 > represented by a separate method.
 >
 > Comments very welcome.
 >
 > Regards,
 >  Mark.
 >
 >
 >

So, I’m using templates for the first time and I wanted to test the case
where the values used by the template don’t exist. I get an error like
this:

    err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Failed to parse template slapd_replication.erb: Could not find
value for 'slapd_consumer_rid' at
/etc/puppet/manifests/experimental/services/ldap.pp:141 on node
t-corp-ldap-03
    warning: Not using cache on failed catalog
    err: Could not retrieve catalog; skipping run

That’s fine. I want it to fail and not touch the target file (which is
what happens), but I also want to *know* it failed. The report in Puppet
Dashboard shows a successful run. I imagine the report only counts
something as a failure if it attempts to do it, but since the template
can’t even be parsed, it’s not trying. Is there some clever thing I can
do to make it fail in a way that will get reported?

One possibility I’ve considered is to check for the variable in the
template and set an invalid default if it’s missing, which will kill LDAP
services on that node. While that would certainly get noticed, I’d prefer
something less extreme.

And a related question: I’d like to store templates in the same
directory that 'puppet://puppet/files/' points to, but I don’t want to
hard-code the path in my manifests. Is there a variable that refers to that
path? (Yeah, I know. Modules. I’m not using them and not planning to any
time soon, so any other ideas would be appreciated.)

Thanks.



Don't try to tell me something is important to you if the whole of your
“support” entails getting Congress to force *others* to spend time and
money on it.

Hi all ,
When I build distribution module I got this failure :

POM Location: /x1/code/cxf/trunk/distribution/pom.xml
Validation Messages:
    [0]  'dependencies.dependency.version' is missing for ant:ant
Reason: Failed to validate POM for project org.apache.cxf:apache-cxf
at /x1/code/cxf/trunk/distribution/pom.xml

The version of ant dependency is missing , this error is both in
distrubition/pom.xml and distrubition/manifest/pom.xml.
Do we use a wrong groupid ?  Can someone help me verify this ?

        <dependency>
            <groupId>ant</groupId>
            <artifactId>ant</artifactId>
        </dependency>

Thanks
Jim

Hello,

I'm a new question asker here but I'll try to give you all the
information you need.
I'm trying to bootstrap a 3rd node into a two node cluster.  I am
specifying an InitialToken of 0 for the new node.  I have replication
factor set to 2, and am using the RackAwareStrategy with digg's
PropertyFileEndPointSnitch.  I'm using an /etc/hosts file to map ips
to short hostnames which the interface bindings and seeds in the
config files use.   Here is what the ring looks like before I attempt
to bootstrap the new node:

$ apache-cassandra-0.6.3/bin/nodetool -h localhost ring
Address       Status     Load          Range
           Ring

138705532905298861485169149262903205000
10.198.7.143  Up         4.57 GB
85070591730234615865843651857942052864     |<--|
10.211.71.241 Up         7.13 GB
138705532905298861485169149262903205000    |-->|

This is with cassandra 0.6.3 obviously.  The exception I get is:

java.lang.AssertionError
	at
org.apache.cassandra.dht.BootStrapper.getRangesWithSources(BootStrapper.java:146)
	at
org.apache.cassandra.dht.BootStrapper.startBootstrap(BootStrapper.java:72)
	at
org.apache.cassandra.service.StorageService.startBootstrap(StorageService.java:406)
	at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:358)
	at
org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:115)
	at
org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:211)

I've posted the full debug log, minus the verbose row mutation messages,
here:

https://gist.github.com/11fc9eddd524e269e490

I see in the code that the tokenMetadata_ is supposed to have a
non-zero number of tokens in it, which it looks like should be created
by updateNormalToken.  I have no idea why this isn't happening in my
case, however.

Thanks in advance for any ideas,

Andy Skalet

Hi

I have a route like this:

<route>
	<from
uri="ftp:localhost/inbox/?username=camel&amp;password=camel123&amp;disconnect=true&amp;consumer.delay=60s&amp;maximumReconnectAttempts=0"
/>
			<to uri="file:test_data" />
</route>

In order to prevent user lock out if the wrong password is provided I
would
like to try and login only once. With this route Camel makes two
connections
at the same time in case the first connection cannot login. Is this
behaviour intended? After some time an exception gets thrown. Preferably I
would like this exception as soon as the client can't login.

(002607) 21-07-2010 10:28:34 - (not logged in) (127.0.0.1)> Connected,
sending welcome message...
(002607) 21-07-2010 10:28:34 - (not logged in) (127.0.0.1)>
220-FileZilla
Server version 0.9.34 beta
(002607) 21-07-2010 10:28:34 - (not logged in) (127.0.0.1)> 220-written
by
Tim Kosse (Tim.K### @gmx.de)
(002607) 21-07-2010 10:28:34 - (not logged in) (127.0.0.1)> 220 Please
visit
http://sourceforge.net/projects/filezilla/
(002607) 21-07-2010 10:28:39 - (not logged in) (127.0.0.1)> USER camel
(002607) 21-07-2010 10:28:39 - (not logged in) (127.0.0.1)> 331
Password
required for camel
(002607) 21-07-2010 10:28:45 - (not logged in) (127.0.0.1)> PASS
*******
(002607) 21-07-2010 10:28:45 - (not logged in) (127.0.0.1)> 530 Login
or
password incorrect!
(002608) 21-07-2010 10:28:45 - (not logged in) (127.0.0.1)> Connected,
sending welcome message...
(002608) 21-07-2010 10:28:45 - (not logged in) (127.0.0.1)>
220-FileZilla
Server version 0.9.34 beta
(002608) 21-07-2010 10:28:45 - (not logged in) (127.0.0.1)> 220-written
by
Tim Kosse (Tim.K### @gmx.de)
(002608) 21-07-2010 10:28:45 - (not logged in) (127.0.0.1)> 220 Please
visit
http://sourceforge.net/projects/filezilla/
(002608) 21-07-2010 10:28:51 - (not logged in) (127.0.0.1)> USER camel
(002608) 21-07-2010 10:28:51 - (not logged in) (127.0.0.1)> 331
Password
required for camel
(002608) 21-07-2010 10:28:57 - (not logged in) (127.0.0.1)> PASS
*******
(002608) 21-07-2010 10:28:57 - (not logged in) (127.0.0.1)> 530 Login
or
password incorrect!
(002608) 21-07-2010 10:29:15 - (not logged in) (127.0.0.1)> QUIT
(002608) 21-07-2010 10:29:15 - (not logged in) (127.0.0.1)> 221 Goodbye
(002608) 21-07-2010 10:29:15 - (not logged in) (127.0.0.1)>
disconnected.
(002607) 21-07-2010 10:29:22 - (not logged in) (127.0.0.1)>
disconnected.

WARNING: Trying to recover by disconnecting from remote server forcing a
re-connect at next poll: ftp://cam### @localhost:21
21-07-2010 10:29:15
org.apache.camel.impl.DefaultPollingConsumerPollStrategy
rollback
WARNING: Consumer
Consumer[ftp://localhost/inbox/?consumer.delay...mp;username=camel]" rel="nofollow" target="_blank">ftp://localhost/inbox/?consumer.delay...p;username=camel]
could not poll endpoint:
ftp://localhost/inbox/?consumer.delay...mp;username=camel
caused by: File operation failed: 530 Login or password incorrect!
. Code: 530
org.apache.camel.component.file.GenericFileOperationFailedException: File
operation failed: 530 Login or password incorrect!
. Code: 530
	at
org.apache.camel.component.file.remote.FtpOperations.connect(FtpOperations.java:161)