[jira] [Commented] (ZOOKEEPER-2170) Zookeeper is not logging as per the configuraiton in log4j.properties
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516397#comment-14516397
]
Arshad Mohammad commented on ZOOKEEPER-2170:
Thanks [~cnauroth] for looking into the issue again.
The patch ZOOKEEPER-2170.001.patch is slightly in different direction.
My concern is simply that default logging should be as per the log4j.properties.
{quote}
BTW, if your goal is just to get the debug logging on with a small simple
log4j.properties change, then maybe the simplest thing is just to change the
root logger setting completely so that it bypasses the environment variables
and system properties:
{code}
#log4j.rootLogger=${zookeeper.root.logger}
log4j.rootLogger=DEBUG, CONSOLE
{code}
{quote}
This issue is not about how to make it work. But it is about how it should be
be by default.
{color:red}If other people also feel the same then lets modify the default
behavior otherwise leave as it is. {color}
> Zookeeper is not logging as per the configuraiton in log4j.properties
> --
>
> Key: ZOOKEEPER-2170
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2170
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Arshad Mohammad
>Assignee: Chris Nauroth
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2170.001.patch
>
>
> In conf/log4j.properties default root logger is
> {code}
> zookeeper.root.logger=INFO, CONSOLE
> {code}
> Changing root logger to bellow value or any other value does not change
> logging effect
> {code}
> zookeeper.root.logger=DEBUG, ROLLINGFILE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2173) ZK startup failure should be handled with proper error message
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516327#comment-14516327 ] J.Andreina commented on ZOOKEEPER-2173: --- Thanks [~fournc] for committing the patch. > ZK startup failure should be handled with proper error message > -- > > Key: ZOOKEEPER-2173 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2173 > Project: ZooKeeper > Issue Type: Bug >Reporter: J.Andreina >Assignee: J.Andreina > Fix For: 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-2173.1.patch > > > If any failure during zk Startup (myid file does not exist), then still zk > startup returns as successful (STARTED). > ZK startup failure should be handled with proper error message -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2163) Introduce new ZNode type: container
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516139#comment-14516139
]
Raul Gutierrez Segales commented on ZOOKEEPER-2163:
---
I want to do another — more detailed — pass but I think it generally looks
good. Overloading the ephemeralOwner field is something that probably needs to
be documented carefully and we need to think about how to make container znodes
discoverable (i.e.: how can operators know which znodes are container ones?).
Thoughts?
cc: [~michim], [~phunt], [~fpj], [~hdeng], [~rakeshr]
> Introduce new ZNode type: container
> ---
>
> Key: ZOOKEEPER-2163
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2163
> Project: ZooKeeper
> Issue Type: New Feature
> Components: c client, java client, server
>Affects Versions: 3.5.0
>Reporter: Jordan Zimmerman
>Assignee: Jordan Zimmerman
> Attachments: zookeeper-2163.patch
>
>
> BACKGROUND
>
> A recurring problem for ZooKeeper users is garbage collection of parent
> nodes. Many recipes (e.g. locks, leaders, etc.) call for the creation of a
> parent node under which participants create sequential nodes. When the
> participant is done, it deletes its node. In practice, the ZooKeeper tree
> begins to fill up with orphaned parent nodes that are no longer needed. The
> ZooKeeper APIs don’t provide a way to clean these. Over time, ZooKeeper can
> become unstable due to the number of these nodes.
> CURRENT SOLUTIONS
> ===
> Apache Curator has a workaround solution for this by providing the Reaper
> class which runs in the background looking for orphaned parent nodes and
> deleting them. This isn’t ideal and it would be better if ZooKeeper supported
> this directly.
> PROPOSAL
> =
> ZOOKEEPER-723 and ZOOKEEPER-834 have been proposed to allow EPHEMERAL nodes
> to contain child nodes. This is not optimum as EPHEMERALs are tied to a
> session and the general use case of parent nodes is for PERSISTENT nodes.
> This proposal adds a new node type, CONTAINER. A CONTAINER node is the same
> as a PERSISTENT node with the additional property that when its last child is
> deleted, it is deleted (and CONTAINER nodes recursively up the tree are
> deleted if empty).
> CANONICAL USAGE
>
> {code}
> while ( true) { // or some reasonable limit
> try {
> zk.create(path, ...);
> break;
> } catch ( KeeperException.NoNodeException e ) {
> try {
> zk.createContainer(containerPath, ...);
> } catch ( KeeperException.NodeExistsException ignore) {
>}
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2173) ZK startup failure should be handled with proper error message
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516042#comment-14516042 ] Hudson commented on ZOOKEEPER-2173: --- SUCCESS: Integrated in ZooKeeper-trunk #2674 (See [https://builds.apache.org/job/ZooKeeper-trunk/2674/]) ZOOKEEPER-2173. ZK startup failure should be handled with proper error message (J.Andreina via camille) (camille: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1676359) * /zookeeper/trunk/CHANGES.txt * /zookeeper/trunk/bin/zkServer.sh > ZK startup failure should be handled with proper error message > -- > > Key: ZOOKEEPER-2173 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2173 > Project: ZooKeeper > Issue Type: Bug >Reporter: J.Andreina >Assignee: J.Andreina > Fix For: 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-2173.1.patch > > > If any failure during zk Startup (myid file does not exist), then still zk > startup returns as successful (STARTED). > ZK startup failure should be handled with proper error message -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk-WinVS2008 - Build # 1775 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1775/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 109 lines...] [javacc] File "SimpleCharStream.java" does not exist. Will create one. [javacc] Parser generated successfully. jute: [javac] Compiling 39 source files to f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\build\classes compile_jute_uptodate: compile_jute: [mkdir] Created dir: f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\generated [mkdir] Created dir: f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\generated [java] ../../zookeeper.jute Parsed Successfully [java] ../../zookeeper.jute Parsed Successfully [touch] Creating f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\generated\.generated BUILD SUCCESSFUL Total time: 8 seconds [ZooKeeper-trunk-WinVS2008] $ cmd /c call C:\Windows\TEMP\hudson217147835344897136.bat f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>set ZOOKEEPER_HOME=f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>msbuild trunk/src/c/zookeeper.sln /p:Configuration=Release Microsoft (R) Build Engine version 4.0.30319.18408 [Microsoft .NET Framework, version 4.0.30319.18444] Copyright (C) Microsoft Corporation. All rights reserved. Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. Build started 4/28/2015 1:26:46 AM. Project "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" on node 1 (default targets). ValidateSolutionConfiguration: Building solution configuration "Release|Win32". zookeeper: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\..\..\vc\vcpackages\VCBuild.exe f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.vcproj "Release|Win32" cl : Command line warning D9035: option 'Wp64' has been deprecated and will be removed in a future release [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] .\src\zookeeper.c(43): fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] Cli: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\..\..\vc\vcpackages\VCBuild.exe f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\Cli.vcproj "Release|Win32" Done Building Project "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default targets) -- FAILED. Build FAILED. "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default target) (1) -> (zookeeper target) -> cl : Command line warning D9035: option 'Wp64' has been deprecated and will be removed in a future release [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default target) (1) -> (zookeeper target) -> .\src\zookeeper.c(43): fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] 1 Warning(s) 1 Error(s) Time Elapsed 00:00:05.46 f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>exit 1 Build step 'Execute Windows batch command' marked build as failure Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Updated] (ZOOKEEPER-2173) ZK startup failure should be handled with proper error message
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Camille Fournier updated ZOOKEEPER-2173: Fix Version/s: 3.6.0 3.5.1 > ZK startup failure should be handled with proper error message > -- > > Key: ZOOKEEPER-2173 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2173 > Project: ZooKeeper > Issue Type: Bug >Reporter: J.Andreina >Assignee: J.Andreina > Fix For: 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-2173.1.patch > > > If any failure during zk Startup (myid file does not exist), then still zk > startup returns as successful (STARTED). > ZK startup failure should be handled with proper error message -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Apache ZooKeeper release 3.5.1-alpha candidate 0
You can go a head and check it in. On Mon, Apr 27, 2015 at 11:40 AM, Camille Fournier wrote: > Is it a problem if I put ZOOKEEPER-2173 into the 3.5 branch before this > release? https://issues.apache.org/jira/browse/ZOOKEEPER-2173 > > On Mon, Apr 27, 2015 at 2:08 AM, Raúl Gutiérrez Segalés > wrote: > >> Hi Michi, >> >> On 26 April 2015 at 14:44, Michi Mutsuzaki wrote: >> >> > Thank you everybody for voting. We are *not* releasing this candidate. >> > There are 2 things to fix: >> > >> > - Update winconfig.h and the notice file (Michi) >> > - https://issues.apache.org/jira/browse/ZOOKEEPER-2171 (Raul?) >> > >> >> I'll get to ZK-2171 tomorrow. >> >> >> -rgs >> >> >> >> > I'll create another candidate once these 2 issues are fixed. >> > >> > >> > On Tue, Apr 21, 2015 at 11:09 AM, Michi Mutsuzaki >> > wrote: >> > > Thanks Pat, I'll update winconfig.h and the notice file. >> > > >> > > On Tue, Apr 21, 2015 at 10:53 AM, Patrick Hunt >> wrote: >> > >> Looks like version strings are in src/c/include/winconfig.h that need >> > to be >> > >> updated. They are still listed as 3.5.0. >> > >> >> > >> I think you'll need to spin a new RC to address this. >> > >> >> > >> You might update the notice file to include 2015 at the same time >> (not a >> > >> blocker typically though). >> > >> >> > >> Patrick >> > >> >> > >> On Mon, Apr 20, 2015 at 5:41 PM, Raúl Gutiérrez Segalés < >> > r...@itevenworks.net >> > >>> wrote: >> > >> >> > >>> On 20 April 2015 at 13:03, Raúl Gutiérrez Segalés < >> r...@itevenworks.net >> > > >> > >>> wrote: >> > >>> >> > >>> > -1, alas. >> > >>> > >> > >>> > I think ZOOKEEPER-1506 could be problematic for some setups. After >> a >> > >>> > couple of elections with a cluster of 5 participants and one >> > observer, I >> > >>> > end up with a participant that's unable to find the leader because >> it >> > >>> does >> > >>> > a reverse lookup (IP -> hostname) and ends up with a bogus hostname >> > that >> > >>> it >> > >>> > can't resolve: >> > >>> > >> > >>> > https://gist.github.com/rgs1/d11822799fdbbfa5d5f2 >> > >>> > >> > >>> > I don't think the reverse lookup from QuorumCnxManager was done >> > before, >> > >>> > nor that it should be done. So it could cause issues in places >> where >> > >>> > reverse lookups aren't fully working. Surely, we could argue that >> > it's a >> > >>> > DNS setup issue but I think we should avoid the extra lookup if >> > possible. >> > >>> > >> > >>> > I'll dig in a bit deeper and try to come with a deterministic >> repro. >> > >>> > >> > >>> >> > >>> Commented on ZOOKEEPER-1506: turns out that my issue was with reverse >> > >>> lookup calls that were not introduced by that patch. They seem to >> have >> > been >> > >>> introduced by ZOOKEEPER-107, so they have been around for a while. >> > >>> >> > >>> The tl;dr is that if your resolvers give you bad reverse names, >> you'll >> > have >> > >>> issues. It would nice to avoid these reverse lookups, so I created: >> > >>> >> > >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2171 >> > >>> >> > >>> After sorting this issue, I tested the following: >> > >>> >> > >>> * many elections (which look quick) >> > >>> * creating and deleting ephemerals in a loop (via zk-shell) >> > >>> * phunt's smoke test scripts (comparable results to 3.5.0) >> > >>> * partitioning and unpartioning an attached observer >> > >>> * use zktraffic's fle-dump & zab-dump to inspect if there were any >> > bogus >> > >>> FLE votes or ZAB messages [0] >> > >>> >> > >>> All of this looks good! So +1 now :-) >> > >>> >> > >>> >> > >>> -rgs >> > >>> >> > >>> p.s.: fwiw, here's my test setup: http://itevenworks.net/zk-releases >> > >>> >> > >>> [0] https://github.com/twitter/zktraffic >> > >>> >> > >>> >> > >>> >> > >>> > >> > >>> > -rgs >> > >>> > >> > >>> > >> > >>> > >> > >>> > >> > >>> > On 12 April 2015 at 14:58, Michi Mutsuzaki >> > >>> wrote: >> > >>> > >> > >>> >> This is a release candidate for 3.5.1-alpha. The full release >> notes >> > is >> > >>> >> available at: >> > >>> >> >> > >>> >> >> > >>> >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12326786 >> > >>> >> >> > >>> >> *** Please download, test and vote by April 25th 2015, 23:59 >> UTC+0. >> > *** >> > >>> >> >> > >>> >> Source files: >> > >>> >> >> http://people.apache.org/~michim/zookeeper-3.5.1-alpha-candidate-0/ >> > >>> >> >> > >>> >> Maven staging repo: >> > >>> >> >> > >>> >> >> > >>> >> > >> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.1-alpha/ >> > >>> >> >> > >>> >> The tag to be voted upon: >> > >>> >> >> https://svn.apache.org/repos/asf/zookeeper/tags/release-3.5.1-rc0/ >> > >>> >> >> > >>> >> ZooKeeper's KEYS file containing PGP keys we use to sign the >> > release: >> > >>> >> http://www.apache.org/dist/zookeeper/KEYS >> > >>> >> >> > >>> >> Should we release this candidate? >> > >>> >> >> > >>> >> --Michi >> > >>> >> >> > >>> > >> > >>> > >> > >>> >> > >>
[jira] [Commented] (ZOOKEEPER-2062) RemoveWatchesTest takes forever to run
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14515020#comment-14515020
]
Chris Nauroth commented on ZOOKEEPER-2062:
--
I just spotted ZOOKEEPER-1274 tracking an enhancement to include child watches
in the watch reports for {{wchc}} and {{wchp}}. I'm linking the issues for the
benefit of anyone who stumbles onto this conversation later.
> RemoveWatchesTest takes forever to run
> --
>
> Key: ZOOKEEPER-2062
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2062
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
>Affects Versions: 3.5.0
>Reporter: Flavio Junqueira
>Assignee: Chris Nauroth
> Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch,
> ZOOKEEPER-2062.003.patch
>
>
> [junit] Running org.apache.zookeeper.RemoveWatchesTest
> [junit] Tests run: 46, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 306.188 sec
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Success: ZOOKEEPER-2062 PreCommit Build #2652
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2062 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2652/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 367030 lines...] [exec] +1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12728495/ZOOKEEPER-2062.003.patch [exec] against trunk revision 1676359. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2652//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2652//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2652//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 6cfa370fadcb0e02d36fc192698b9f64f5fb4ed5 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 47 minutes 58 seconds Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2650 Archived 24 artifacts Archive block size is 32768 Received 7 blocks and 33707166 bytes Compression is 0.7% Took 11 sec Recording test results Description set: ZOOKEEPER-2062 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2062) RemoveWatchesTest takes forever to run
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514960#comment-14514960 ] Hadoop QA commented on ZOOKEEPER-2062: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12728495/ZOOKEEPER-2062.003.patch against trunk revision 1676359. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2652//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2652//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2652//console This message is automatically generated. > RemoveWatchesTest takes forever to run > -- > > Key: ZOOKEEPER-2062 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2062 > Project: ZooKeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.5.0 >Reporter: Flavio Junqueira >Assignee: Chris Nauroth > Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch, > ZOOKEEPER-2062.003.patch > > > [junit] Running org.apache.zookeeper.RemoveWatchesTest > [junit] Tests run: 46, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 306.188 sec -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2062) RemoveWatchesTest takes forever to run
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated ZOOKEEPER-2062:
-
Attachment: ZOOKEEPER-2062.003.patch
I'm attaching patch v003. This brings the whole test suite run down to 1
minute 20 seconds on my machine.
This applies the suggestions from the last comment from Rakesh. As mentioned
in my last comment though, I found that {{DataTree#getWatchesByPath}} returned
only data watches. Instead of relying on that, I've added assertions on
whether or not the server-side session is registered as a watcher. Let me know
if this is sufficient.
{{testRemoveSingleWatcher}} and {{testMultipleDataWatchers}} are still a tad
slow. However, I didn't want to change these, because it seems these are
specifically intended to check session close semantics. Once the session is
closed, trying to do these new assertions wouldn't be valid, so I left these
tests waiting on the latches for timeouts.
I also didn't change the {{*NoConnection}} tests. It seems the only option
here would be to downtune client timeout settings, which could get finicky.
I verified again that introducing bugs in {{ZKDatabase}} causes test failures,
so the tests are still capable of catching regressions.
Rakesh and Camille, what do you think of this version? Thanks again for your
guidance!
> RemoveWatchesTest takes forever to run
> --
>
> Key: ZOOKEEPER-2062
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2062
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
>Affects Versions: 3.5.0
>Reporter: Flavio Junqueira
>Assignee: Chris Nauroth
> Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch,
> ZOOKEEPER-2062.003.patch
>
>
> [junit] Running org.apache.zookeeper.RemoveWatchesTest
> [junit] Tests run: 46, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 306.188 sec
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2170) Zookeeper is not logging as per the configuraiton in log4j.properties
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514705#comment-14514705
]
Chris Nauroth commented on ZOOKEEPER-2170:
--
bq. -1 tests included. The patch doesn't appear to include any new or modified
tests.
No new tests were added, because it's a configuration change only.
> Zookeeper is not logging as per the configuraiton in log4j.properties
> --
>
> Key: ZOOKEEPER-2170
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2170
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Arshad Mohammad
>Assignee: Chris Nauroth
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2170.001.patch
>
>
> In conf/log4j.properties default root logger is
> {code}
> zookeeper.root.logger=INFO, CONSOLE
> {code}
> Changing root logger to bellow value or any other value does not change
> logging effect
> {code}
> zookeeper.root.logger=DEBUG, ROLLINGFILE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2170) Zookeeper is not logging as per the configuraiton in log4j.properties
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514692#comment-14514692
]
Hadoop QA commented on ZOOKEEPER-2170:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12728464/ZOOKEEPER-2170.001.patch
against trunk revision 1672934.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2651//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2651//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2651//console
This message is automatically generated.
> Zookeeper is not logging as per the configuraiton in log4j.properties
> --
>
> Key: ZOOKEEPER-2170
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2170
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Arshad Mohammad
>Assignee: Chris Nauroth
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2170.001.patch
>
>
> In conf/log4j.properties default root logger is
> {code}
> zookeeper.root.logger=INFO, CONSOLE
> {code}
> Changing root logger to bellow value or any other value does not change
> logging effect
> {code}
> zookeeper.root.logger=DEBUG, ROLLINGFILE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2170 PreCommit Build #2651
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2170 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2651/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 361285 lines...] [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2651//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2651//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2651//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 68e6851a448fff3a131dbf076fcba26c6c62422c logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1721: exec returned: 1 Total time: 52 minutes 9 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2650 Archived 24 artifacts Archive block size is 32768 Received 7 blocks and 33352342 bytes Compression is 0.7% Took 18 sec Recording test results Description set: ZOOKEEPER-2170 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## All tests passed
Re: [VOTE] Apache ZooKeeper release 3.5.1-alpha candidate 0
Is it a problem if I put ZOOKEEPER-2173 into the 3.5 branch before this release? https://issues.apache.org/jira/browse/ZOOKEEPER-2173 On Mon, Apr 27, 2015 at 2:08 AM, Raúl Gutiérrez Segalés wrote: > Hi Michi, > > On 26 April 2015 at 14:44, Michi Mutsuzaki wrote: > > > Thank you everybody for voting. We are *not* releasing this candidate. > > There are 2 things to fix: > > > > - Update winconfig.h and the notice file (Michi) > > - https://issues.apache.org/jira/browse/ZOOKEEPER-2171 (Raul?) > > > > I'll get to ZK-2171 tomorrow. > > > -rgs > > > > > I'll create another candidate once these 2 issues are fixed. > > > > > > On Tue, Apr 21, 2015 at 11:09 AM, Michi Mutsuzaki > > wrote: > > > Thanks Pat, I'll update winconfig.h and the notice file. > > > > > > On Tue, Apr 21, 2015 at 10:53 AM, Patrick Hunt > wrote: > > >> Looks like version strings are in src/c/include/winconfig.h that need > > to be > > >> updated. They are still listed as 3.5.0. > > >> > > >> I think you'll need to spin a new RC to address this. > > >> > > >> You might update the notice file to include 2015 at the same time > (not a > > >> blocker typically though). > > >> > > >> Patrick > > >> > > >> On Mon, Apr 20, 2015 at 5:41 PM, Raúl Gutiérrez Segalés < > > r...@itevenworks.net > > >>> wrote: > > >> > > >>> On 20 April 2015 at 13:03, Raúl Gutiérrez Segalés < > r...@itevenworks.net > > > > > >>> wrote: > > >>> > > >>> > -1, alas. > > >>> > > > >>> > I think ZOOKEEPER-1506 could be problematic for some setups. After > a > > >>> > couple of elections with a cluster of 5 participants and one > > observer, I > > >>> > end up with a participant that's unable to find the leader because > it > > >>> does > > >>> > a reverse lookup (IP -> hostname) and ends up with a bogus hostname > > that > > >>> it > > >>> > can't resolve: > > >>> > > > >>> > https://gist.github.com/rgs1/d11822799fdbbfa5d5f2 > > >>> > > > >>> > I don't think the reverse lookup from QuorumCnxManager was done > > before, > > >>> > nor that it should be done. So it could cause issues in places > where > > >>> > reverse lookups aren't fully working. Surely, we could argue that > > it's a > > >>> > DNS setup issue but I think we should avoid the extra lookup if > > possible. > > >>> > > > >>> > I'll dig in a bit deeper and try to come with a deterministic > repro. > > >>> > > > >>> > > >>> Commented on ZOOKEEPER-1506: turns out that my issue was with reverse > > >>> lookup calls that were not introduced by that patch. They seem to > have > > been > > >>> introduced by ZOOKEEPER-107, so they have been around for a while. > > >>> > > >>> The tl;dr is that if your resolvers give you bad reverse names, > you'll > > have > > >>> issues. It would nice to avoid these reverse lookups, so I created: > > >>> > > >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2171 > > >>> > > >>> After sorting this issue, I tested the following: > > >>> > > >>> * many elections (which look quick) > > >>> * creating and deleting ephemerals in a loop (via zk-shell) > > >>> * phunt's smoke test scripts (comparable results to 3.5.0) > > >>> * partitioning and unpartioning an attached observer > > >>> * use zktraffic's fle-dump & zab-dump to inspect if there were any > > bogus > > >>> FLE votes or ZAB messages [0] > > >>> > > >>> All of this looks good! So +1 now :-) > > >>> > > >>> > > >>> -rgs > > >>> > > >>> p.s.: fwiw, here's my test setup: http://itevenworks.net/zk-releases > > >>> > > >>> [0] https://github.com/twitter/zktraffic > > >>> > > >>> > > >>> > > >>> > > > >>> > -rgs > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > On 12 April 2015 at 14:58, Michi Mutsuzaki > > >>> wrote: > > >>> > > > >>> >> This is a release candidate for 3.5.1-alpha. The full release > notes > > is > > >>> >> available at: > > >>> >> > > >>> >> > > >>> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12326786 > > >>> >> > > >>> >> *** Please download, test and vote by April 25th 2015, 23:59 > UTC+0. > > *** > > >>> >> > > >>> >> Source files: > > >>> >> > http://people.apache.org/~michim/zookeeper-3.5.1-alpha-candidate-0/ > > >>> >> > > >>> >> Maven staging repo: > > >>> >> > > >>> >> > > >>> > > > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.1-alpha/ > > >>> >> > > >>> >> The tag to be voted upon: > > >>> >> > https://svn.apache.org/repos/asf/zookeeper/tags/release-3.5.1-rc0/ > > >>> >> > > >>> >> ZooKeeper's KEYS file containing PGP keys we use to sign the > > release: > > >>> >> http://www.apache.org/dist/zookeeper/KEYS > > >>> >> > > >>> >> Should we release this candidate? > > >>> >> > > >>> >> --Michi > > >>> >> > > >>> > > > >>> > > > >>> > > >
[jira] [Commented] (ZOOKEEPER-2173) ZK startup failure should be handled with proper error message
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514648#comment-14514648 ] Camille Fournier commented on ZOOKEEPER-2173: - This is great, +1. I will check it in. > ZK startup failure should be handled with proper error message > -- > > Key: ZOOKEEPER-2173 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2173 > Project: ZooKeeper > Issue Type: Bug >Reporter: J.Andreina >Assignee: J.Andreina > Attachments: ZOOKEEPER-2173.1.patch > > > If any failure during zk Startup (myid file does not exist), then still zk > startup returns as successful (STARTED). > ZK startup failure should be handled with proper error message -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2062) RemoveWatchesTest takes forever to run
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514617#comment-14514617
]
Chris Nauroth commented on ZOOKEEPER-2062:
--
I also wanted to mention that {{DataTree#getWatchesByPath}} returns only data
watchers (not child watchers), so I modified the suggestion from Rakesh a bit
to check if the {{ServerCnxn}} is registered as a watcher for covering both
cases. Thanks for the help Rakesh!
> RemoveWatchesTest takes forever to run
> --
>
> Key: ZOOKEEPER-2062
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2062
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
>Affects Versions: 3.5.0
>Reporter: Flavio Junqueira
>Assignee: Chris Nauroth
> Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch
>
>
> [junit] Running org.apache.zookeeper.RemoveWatchesTest
> [junit] Tests run: 46, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 306.188 sec
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2171) avoid reverse lookups in QuorumCnxManager
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514612#comment-14514612 ] Camille Fournier commented on ZOOKEEPER-2171: - I see a bunch of references throughout the project beyond QCM. Is it just QCM that needs updating? > avoid reverse lookups in QuorumCnxManager > - > > Key: ZOOKEEPER-2171 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2171 > Project: ZooKeeper > Issue Type: Bug > Components: quorum >Reporter: Raul Gutierrez Segales >Assignee: Raul Gutierrez Segales > Fix For: 3.5.1, 3.6.0 > > > Apparently, ZOOKEEPER-107 (via a quick git-blame look) introduced a bunch of > getHostName() calls in QCM. Besides the overhead, these can cause problems > when mixed with failing/mis-configured DNS servers. > It would be nice to reduce them, if that doesn't affect operational > correctness. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2062) RemoveWatchesTest takes forever to run
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514607#comment-14514607 ] Chris Nauroth commented on ZOOKEEPER-2062: -- Thanks, Camille. I've got something in progress making similar changes across the suite. > RemoveWatchesTest takes forever to run > -- > > Key: ZOOKEEPER-2062 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2062 > Project: ZooKeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.5.0 >Reporter: Flavio Junqueira >Assignee: Chris Nauroth > Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch > > > [junit] Running org.apache.zookeeper.RemoveWatchesTest > [junit] Tests run: 46, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 306.188 sec -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2062) RemoveWatchesTest takes forever to run
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514596#comment-14514596 ] Camille Fournier commented on ZOOKEEPER-2062: - I dig this a bunch. [~rakeshr] if you wanna upload an updated patch with your changes I will review it and pending my +1 you can check it in. > RemoveWatchesTest takes forever to run > -- > > Key: ZOOKEEPER-2062 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2062 > Project: ZooKeeper > Issue Type: Bug > Components: tests >Affects Versions: 3.5.0 >Reporter: Flavio Junqueira >Assignee: Chris Nauroth > Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch > > > [junit] Running org.apache.zookeeper.RemoveWatchesTest > [junit] Tests run: 46, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 306.188 sec -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2170) Zookeeper is not logging as per the configuraiton in log4j.properties
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated ZOOKEEPER-2170:
-
Attachment: ZOOKEEPER-2170.001.patch
Thank you, Arshad. I know existing deployments are dependent on the current
setup with these environment variables and system properties, so I'm inclined
to leave it mostly intact. However, I also think needing to set 2 separate
properties to achieve debug logging is a bit cumbersome.
Maybe one thing we could safely do here is to set the thresholding to {{ALL}}.
(Patch attached.) With that in place, you could set just {{ZOO_LOG4J_PROP}} to
achieve debug logging. ZOOKEEPER-980 states that the goal was consistency with
Hadoop's logging configuration, and Hadoop sets thresholding to {{ALL}}.
This could still be seen as a backwards-incompatible change if admins were
dependent on the existing thresholding. Maybe this change still can go into
trunk though. I'm not familiar with ZooKeeper's versioning and compatibility
guidelines, so I'll need to defer to established contributors to make that call.
BTW, if your goal is just to get the debug logging on with a small simple
log4j.properties change, then maybe the simplest thing is just to change the
root logger setting completely so that it bypasses the environment variables
and system properties:
{code}
#log4j.rootLogger=${zookeeper.root.logger}
log4j.rootLogger=DEBUG, CONSOLE
{code}
> Zookeeper is not logging as per the configuraiton in log4j.properties
> --
>
> Key: ZOOKEEPER-2170
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2170
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Arshad Mohammad
>Assignee: Chris Nauroth
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2170.001.patch
>
>
> In conf/log4j.properties default root logger is
> {code}
> zookeeper.root.logger=INFO, CONSOLE
> {code}
> Changing root logger to bellow value or any other value does not change
> logging effect
> {code}
> zookeeper.root.logger=DEBUG, ROLLINGFILE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (ZOOKEEPER-2170) Zookeeper is not logging as per the configuraiton in log4j.properties
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth reopened ZOOKEEPER-2170:
--
> Zookeeper is not logging as per the configuraiton in log4j.properties
> --
>
> Key: ZOOKEEPER-2170
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2170
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Arshad Mohammad
>Assignee: Chris Nauroth
> Fix For: 3.6.0
>
>
> In conf/log4j.properties default root logger is
> {code}
> zookeeper.root.logger=INFO, CONSOLE
> {code}
> Changing root logger to bellow value or any other value does not change
> logging effect
> {code}
> zookeeper.root.logger=DEBUG, ROLLINGFILE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2139) Zookeeper client configuration should not be java system property
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514109#comment-14514109
]
surendra singh lilhore commented on ZOOKEEPER-2139:
---
Thanks [~rakeshr] for reviewing.. I have one doubt for first comment. If I want
to extend {{AbstractConfiguration}} then I need to add one new dependency for
{{commons-configuration-*.jar}} and it will create compatibility issue. Please
correct if I am wrong.
> Zookeeper client configuration should not be java system property
> -
>
> Key: ZOOKEEPER-2139
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2139
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
>Affects Versions: 3.5.0
>Reporter: surendra singh lilhore
>Assignee: surendra singh lilhore
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2139.patch, ZOOKEEPER-2139_1.patch,
> ZOOKEEPER-2139_2.patch
>
>
> I have two ZK client in one JVM, one is secure client and second is normal
> client (For non secure cluster).
> "zookeeper.sasl.client" system property is "true" by default, because of this
> my second client connection is failing.
> We should pass all client configurations in client constructor like HDFS
> client.
> For example :
> {code}
> public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher,
> Configuration conf) throws IOException
> {
> ..
> ..
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper-trunk-jdk8 - Build # 365 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/365/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 361811 lines...] [junit] 2015-04-27 12:28:07,474 [myid:] - INFO [main:FourLetterWordMain@63] - connecting to 127.0.0.1 11221 [junit] 2015-04-27 12:28:07,475 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2015-04-27 12:28:07,476 [myid:] - INFO [main:ClientBase@461] - STARTING server [junit] 2015-04-27 12:28:07,476 [myid:] - INFO [main:ClientBase@381] - CREATING server instance 127.0.0.1:11221 [junit] 2015-04-27 12:28:07,476 [myid:] - INFO [main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2015-04-27 12:28:07,477 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2015-04-27 12:28:07,477 [myid:] - INFO [main:ClientBase@356] - STARTING server instance 127.0.0.1:11221 [junit] 2015-04-27 12:28:07,477 [myid:] - INFO [main:ZooKeeperServer@825] - minSessionTimeout set to 6000 [junit] 2015-04-27 12:28:07,478 [myid:] - INFO [main:ZooKeeperServer@834] - maxSessionTimeout set to 6 [junit] 2015-04-27 12:28:07,478 [myid:] - INFO [main:ZooKeeperServer@156] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8159374575659869686.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8159374575659869686.junit.dir/version-2 [junit] 2015-04-27 12:28:07,478 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8159374575659869686.junit.dir/version-2/snapshot.b [junit] 2015-04-27 12:28:07,481 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test8159374575659869686.junit.dir/version-2/snapshot.b [junit] 2015-04-27 12:28:07,483 [myid:] - INFO [main:FourLetterWordMain@63] - connecting to 127.0.0.1 11221 [junit] 2015-04-27 12:28:07,484 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:53602 [junit] 2015-04-27 12:28:07,485 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@836] - Processing stat command from /127.0.0.1:53602 [junit] 2015-04-27 12:28:07,486 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@685] - Stat command output [junit] 2015-04-27 12:28:07,486 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:53602 (no session established for client) [junit] 2015-04-27 12:28:07,486 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2015-04-27 12:28:07,488 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2015-04-27 12:28:07,488 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2015-04-27 12:28:07,488 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2015-04-27 12:28:07,488 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2015-04-27 12:28:07,489 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 62027 [junit] 2015-04-27 12:28:07,489 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2015-04-27 12:28:07,489 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2015-04-27 12:28:07,489 [myid:] - INFO [main:ClientBase@538] - tearDown starting [junit] 2015-04-27 12:28:07,554 [myid:] - INFO [main:ZooKeeper@] - Session: 0x104232f4497 closed [junit] 2015-04-27 12:28:07,554 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@531] - EventThread shut down [junit] 2015-04-27 12:28:07,554 [myid:] - INFO [main:ClientBase@508] - STOPPING server [junit] 2015-04-27 12:28:07,555 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2015-04-27 12:28:07,555 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2015-04-27 12:28:07,555 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thre
ZooKeeper-trunk-WinVS2008 - Build # 1774 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1774/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 110 lines...] [javacc] File "SimpleCharStream.java" does not exist. Will create one. [javacc] Parser generated successfully. jute: [javac] Compiling 39 source files to f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\build\classes compile_jute_uptodate: compile_jute: [mkdir] Created dir: f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\generated [mkdir] Created dir: f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\generated [java] ../../zookeeper.jute Parsed Successfully [java] ../../zookeeper.jute Parsed Successfully [touch] Creating f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\generated\.generated BUILD SUCCESSFUL Total time: 7 seconds [ZooKeeper-trunk-WinVS2008] $ cmd /c call C:\Windows\TEMP\hudson2173071736347890531.bat f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>set ZOOKEEPER_HOME=f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>msbuild trunk/src/c/zookeeper.sln /p:Configuration=Release Microsoft (R) Build Engine version 4.0.30319.18408 [Microsoft .NET Framework, version 4.0.30319.18444] Copyright (C) Microsoft Corporation. All rights reserved. Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. Build started 4/27/2015 1:08:12 PM. Project "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" on node 1 (default targets). ValidateSolutionConfiguration: Building solution configuration "Release|Win32". zookeeper: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\..\..\vc\vcpackages\VCBuild.exe f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.vcproj "Release|Win32" cl : Command line warning D9035: option 'Wp64' has been deprecated and will be removed in a future release [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] .\src\zookeeper.c(43): fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] Cli: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\..\..\vc\vcpackages\VCBuild.exe f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\Cli.vcproj "Release|Win32" Done Building Project "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default targets) -- FAILED. Build FAILED. "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default target) (1) -> (zookeeper target) -> cl : Command line warning D9035: option 'Wp64' has been deprecated and will be removed in a future release [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default target) (1) -> (zookeeper target) -> .\src\zookeeper.c(43): fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] 1 Warning(s) 1 Error(s) Time Elapsed 00:00:05.12 f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>exit 1 Build step 'Execute Windows batch command' marked build as failure Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-2173) ZK startup failure should be handled with proper error message
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513942#comment-14513942 ] J.Andreina commented on ZOOKEEPER-2173: --- As this is addition of proper error message if any failure in startup , no need of testcase. > ZK startup failure should be handled with proper error message > -- > > Key: ZOOKEEPER-2173 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2173 > Project: ZooKeeper > Issue Type: Bug >Reporter: J.Andreina >Assignee: J.Andreina > Attachments: ZOOKEEPER-2173.1.patch > > > If any failure during zk Startup (myid file does not exist), then still zk > startup returns as successful (STARTED). > ZK startup failure should be handled with proper error message -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper_branch35_jdk7 - Build # 277 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/277/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 360036 lines...] [junit] 2015-04-27 11:26:40,303 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2015-04-27 11:26:40,305 [myid:] - INFO [main:ClientBase@461] - STARTING server [junit] 2015-04-27 11:26:40,305 [myid:] - INFO [main:ClientBase@381] - CREATING server instance 127.0.0.1:11221 [junit] 2015-04-27 11:26:40,305 [myid:] - INFO [main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2015-04-27 11:26:40,306 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2015-04-27 11:26:40,306 [myid:] - INFO [main:ClientBase@356] - STARTING server instance 127.0.0.1:11221 [junit] 2015-04-27 11:26:40,306 [myid:] - INFO [main:ZooKeeperServer@825] - minSessionTimeout set to 6000 [junit] 2015-04-27 11:26:40,307 [myid:] - INFO [main:ZooKeeperServer@834] - maxSessionTimeout set to 6 [junit] 2015-04-27 11:26:40,307 [myid:] - INFO [main:ZooKeeperServer@156] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/tmp/test191327889587361344.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/tmp/test191327889587361344.junit.dir/version-2 [junit] 2015-04-27 11:26:40,308 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/tmp/test191327889587361344.junit.dir/version-2/snapshot.b [junit] 2015-04-27 11:26:40,310 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/tmp/test191327889587361344.junit.dir/version-2/snapshot.b [junit] 2015-04-27 11:26:40,312 [myid:] - INFO [main:FourLetterWordMain@63] - connecting to 127.0.0.1 11221 [junit] 2015-04-27 11:26:40,312 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:54643 [junit] 2015-04-27 11:26:40,313 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@836] - Processing stat command from /127.0.0.1:54643 [junit] 2015-04-27 11:26:40,313 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@685] - Stat command output [junit] 2015-04-27 11:26:40,313 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:54643 (no session established for client) [junit] 2015-04-27 11:26:40,314 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2015-04-27 11:26:40,315 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2015-04-27 11:26:40,316 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2015-04-27 11:26:40,316 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2015-04-27 11:26:40,316 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2015-04-27 11:26:40,316 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 18131 [junit] 2015-04-27 11:26:40,316 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2015-04-27 11:26:40,316 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2015-04-27 11:26:40,317 [myid:] - INFO [main:ClientBase@538] - tearDown starting [junit] 2015-04-27 11:26:40,383 [myid:] - INFO [main:ZooKeeper@] - Session: 0x10422f701dc closed [junit] 2015-04-27 11:26:40,383 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@531] - EventThread shut down [junit] 2015-04-27 11:26:40,383 [myid:] - INFO [main:ClientBase@508] - STOPPING server [junit] 2015-04-27 11:26:40,384 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2015-04-27 11:26:40,384 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2015-04-27 11:26:40,384 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2015-04-27 11:26:40,384 [myid:] - INFO [NIOServerCxnFactory.A
[jira] [Commented] (ZOOKEEPER-2170) Zookeeper is not logging as per the configuraiton in log4j.properties
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513840#comment-14513840
]
Arshad Mohammad commented on ZOOKEEPER-2170:
Thanks [~cnauroth] for looking into the issue.
It is good that we have option for customizing the logging behaviour through
various ways.
But I think that default behaviour should come from log4j.properties because
this is the place where any user by default will go for changing the log.
If ZOO_LOG4J_PROP values is not set then{color:red} we should not set any
default value{color}, which is being set in zkEnv.sh, also we should not pass
as system property.
Same thing should be done for other such variables like ZOO_LOG_DIR
> Zookeeper is not logging as per the configuraiton in log4j.properties
> --
>
> Key: ZOOKEEPER-2170
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2170
> Project: ZooKeeper
> Issue Type: Bug
>Reporter: Arshad Mohammad
>Assignee: Chris Nauroth
> Fix For: 3.6.0
>
>
> In conf/log4j.properties default root logger is
> {code}
> zookeeper.root.logger=INFO, CONSOLE
> {code}
> Changing root logger to bellow value or any other value does not change
> logging effect
> {code}
> zookeeper.root.logger=DEBUG, ROLLINGFILE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper-trunk-solaris - Build # 1014 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1014/ ### ## LAST 60 LINES OF THE CONSOLE ### Started by timer Building remotely on solaris1 (Solaris) in workspace /export/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris Updating http://svn.apache.org/repos/asf/zookeeper/trunk at revision '2015-04-27T08:31:13.426 +' At revision 1676219 Updating http://svn.apache.org/repos/asf/hadoop/nightly at revision '2015-04-27T08:31:13.426 +' At revision 1676219 no change for http://svn.apache.org/repos/asf/zookeeper/trunk since the previous build no change for http://svn.apache.org/repos/asf/hadoop/nightly since the previous build No emails were triggered. [locks-and-latches] Checking to see if we really have the locks [locks-and-latches] Have all the locks, build can start [ZooKeeper-trunk-solaris] $ /bin/bash /var/tmp/hudson1373779431676836446.sh /var/tmp/hudson1373779431676836446.sh: line 12: ant: command not found Build step 'Execute shell' marked build as failure [locks-and-latches] Releasing all the locks [locks-and-latches] All the locks released Recording test results Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
ZooKeeper-trunk-WinVS2008 - Build # 1773 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1773/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 108 lines...] [javacc] File "SimpleCharStream.java" does not exist. Will create one. [javacc] Parser generated successfully. jute: [javac] Compiling 39 source files to f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\build\classes compile_jute_uptodate: compile_jute: [mkdir] Created dir: f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\generated [mkdir] Created dir: f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\generated [java] ../../zookeeper.jute Parsed Successfully [java] ../../zookeeper.jute Parsed Successfully [touch] Creating f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\java\generated\.generated BUILD SUCCESSFUL Total time: 8 seconds [ZooKeeper-trunk-WinVS2008] $ cmd /c call C:\Windows\TEMP\hudson8413344012297320963.bat f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>set ZOOKEEPER_HOME=f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>msbuild trunk/src/c/zookeeper.sln /p:Configuration=Release Microsoft (R) Build Engine version 4.0.30319.18408 [Microsoft .NET Framework, version 4.0.30319.18444] Copyright (C) Microsoft Corporation. All rights reserved. Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. Build started 4/27/2015 9:23:40 AM. Project "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" on node 1 (default targets). ValidateSolutionConfiguration: Building solution configuration "Release|Win32". zookeeper: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\..\..\vc\vcpackages\VCBuild.exe f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.vcproj "Release|Win32" cl : Command line warning D9035: option 'Wp64' has been deprecated and will be removed in a future release [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] .\src\zookeeper.c(43): fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] Cli: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\..\..\vc\vcpackages\VCBuild.exe f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\Cli.vcproj "Release|Win32" Done Building Project "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default targets) -- FAILED. Build FAILED. "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default target) (1) -> (zookeeper target) -> cl : Command line warning D9035: option 'Wp64' has been deprecated and will be removed in a future release [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] "f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln" (default target) (1) -> (zookeeper target) -> .\src\zookeeper.c(43): fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory [f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008\trunk\src\c\zookeeper.sln] 1 Warning(s) 1 Error(s) Time Elapsed 00:00:08.91 f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008>exit 1 Build step 'Execute Windows batch command' marked build as failure Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
