[
https://issues.apache.org/jira/browse/ZOOKEEPER-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974589#comment-13974589
]
Raul Gutierrez Segales commented on ZOOKEEPER-1913:
---------------------------------------------------
Thanks for the fast reply, [~michim]. I think the failure:
{noformat}
src/c/tests/TestWatchers.cc:667: Assertion: assertion failed [Expression:
ensureCondition( deliveryTracker.deliveryCounterEquals(2),1000)<1000]
{noformat}
is related to old code (i.e.: the test case is testNodeWatcher1, which is old).
Also, in my setup those tests fail very often due to missed timeouts mostly.
> Invalid manifest files due to bogus revision property value
> -----------------------------------------------------------
>
> Key: ZOOKEEPER-1913
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1913
> Project: ZooKeeper
> Issue Type: Bug
> Components: build
> Affects Versions: 3.4.6, 3.5.0
> Reporter: Raul Gutierrez Segales
> Assignee: Raul Gutierrez Segales
> Fix For: 3.4.7, 3.5.0
>
> Attachments: ZOOKEEPER-1913.patch
>
>
> Without the proposed patch, I get invalid manifests because stderr is added
> to the revision property. I think this might be something specific to my
> setup though:
> {noformat}
> $ java -version
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=utf8
> java version "1.7.0_51"
> OpenJDK Runtime Environment (fedora-2.4.5.1.fc20-x86_64 u51-b31)
> OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
> {noformat}
> since it doesn't seem happen with older java/ant combinations.
> Nonetheless, it seems like the right thing is to explicitly ignore stderr.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
