[jira] [Assigned] (ZOOKEEPER-2179) Typo in Watcher.java
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surendra singh lilhore reassigned ZOOKEEPER-2179: - Assignee: surendra singh lilhore > Typo in Watcher.java > > > Key: ZOOKEEPER-2179 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2179 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.4.5, 3.5.0 >Reporter: Eunchan Kim >Assignee: surendra singh lilhore >Priority: Trivial > Fix For: 3.4.5, 3.5.0 > > > at zookeeper/src/java/main/org/apache/zookeeper/Watcher.java, > * implement. A ZooKeeper client will get various events from the ZooKeepr > should be fixed to > * implement. A ZooKeeper client will get various events from the ZooKeeper. > (Zookeepr -> Zookeeper) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2180) quota do not take effect in version 3.4.6
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surendra singh lilhore reassigned ZOOKEEPER-2180: - Assignee: surendra singh lilhore > quota do not take effect in version 3.4.6 > - > > Key: ZOOKEEPER-2180 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2180 > Project: ZooKeeper > Issue Type: Bug > Environment: zookeeper version 3.4.6 >Reporter: seekerak >Assignee: surendra singh lilhore > > [zk: localhost:2181(CONNECTED) 18] listquota /mynode > absolute path is /zookeeper/quota/mynode/zookeeper_limits > Output quota for /mynode count=-1,bytes=100 > Output stat for /mynode count=6,bytes=484 > [zk: localhost:2181(CONNECTED) 19] listquota /mynode_n > absolute path is /zookeeper/quota/mynode_n/zookeeper_limits > Output quota for /mynode_n count=2,bytes=-1 > Output stat for /mynode_n count=5,bytes=5 -- 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=14527873#comment-14527873 ] Chris Nauroth commented on ZOOKEEPER-2062: -- [~rakeshr], thank you for the helpful code review feedback and the commit! > 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 > Fix For: 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch, > ZOOKEEPER-2062.003.patch, ZOOKEEPER-2062.004.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-2096) C client builds with incorrect error codes in VisualStudio 2010+
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527864#comment-14527864 ] Hadoop QA commented on ZOOKEEPER-2096: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12730339/ZOOKEEPER-2096.patch against trunk revision 1677724. +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/2678//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2678//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2678//console This message is automatically generated. > C client builds with incorrect error codes in VisualStudio 2010+ > > > Key: ZOOKEEPER-2096 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2096 > Project: ZooKeeper > Issue Type: Bug > Components: build, c client > Environment: Windows MSVS 2010+ >Reporter: Vitaly Stakhovsky > Attachments: ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch, > ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > It reports: > warning C4005: 'EWOULDBLOCK' : macro redefinition > warning C4005: 'EINPROGRESS' : macro redefinition > In MSVS 2010+, these constants are now in . > What's worse, they have different numeric values. > Possible fix: > In "src/c/include/winconfig.h" : > #if _MSC_VER < 1600 > #define EWOULDBLOCK WSAEWOULDBLOCK > #define EINPROGRESS WSAEINPROGRESS > #endif -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2096 PreCommit Build #2678
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2096 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2678/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 363789 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/2678//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2678//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2678//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] a5b69c04b6033509b69346663ce3a9f8c25fbcec 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:1732: exec returned: 1 Total time: 47 minutes 41 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2674 Archived 24 artifacts Archive block size is 32768 Received 6 blocks and 33577204 bytes Compression is 0.6% Took 9.7 sec Recording test results Description set: ZOOKEEPER-2096 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## All tests passed
[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 ] Rakesh R updated ZOOKEEPER-2062: Fix Version/s: (was: 3.5.2) 3.5.1 > 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 > Fix For: 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch, > ZOOKEEPER-2062.003.patch, ZOOKEEPER-2062.004.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=14527805#comment-14527805 ] Rakesh R commented on ZOOKEEPER-2062: - Thanks [~cnauroth] for the contribution! Committed to trunk : http://svn.apache.org/viewvc?view=revision&revision=1677724 Committed to br3.5 : http://svn.apache.org/viewvc?view=revision&revision=1677726 > 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 > Fix For: 3.5.1, 3.6.0 > > Attachments: ZOOKEEPER-2062.001.patch, ZOOKEEPER-2062.002.patch, > ZOOKEEPER-2062.003.patch, ZOOKEEPER-2062.004.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-2180) quota do not take effect in version 3.4.6
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] seekerak updated ZOOKEEPER-2180: Description: [zk: localhost:2181(CONNECTED) 18] listquota /mynode absolute path is /zookeeper/quota/mynode/zookeeper_limits Output quota for /mynode count=-1,bytes=100 Output stat for /mynode count=6,bytes=484 [zk: localhost:2181(CONNECTED) 19] listquota /mynode_n absolute path is /zookeeper/quota/mynode_n/zookeeper_limits Output quota for /mynode_n count=2,bytes=-1 Output stat for /mynode_n count=5,bytes=5 was: [zk: localhost:2181(CONNECTED) 18] listquota /mynode absolute path is /zookeeper/quota/mynode/zookeeper_limits Output quota for /mynode count=-1,bytes=100 Output stat for /mynode count=6,bytes=484 [zk: localhost:2181(CONNECTED) 19] listquota /mynode_n absolute path is /zookeeper/quota/mynode_n/zookeeper_limits Output quota for /mynode_n count=2,bytes=-1 Output stat for /mynode_n count=5,bytes=5 > quota do not take effect in version 3.4.6 > - > > Key: ZOOKEEPER-2180 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2180 > Project: ZooKeeper > Issue Type: Bug > Environment: zookeeper version 3.4.6 >Reporter: seekerak > > [zk: localhost:2181(CONNECTED) 18] listquota /mynode > absolute path is /zookeeper/quota/mynode/zookeeper_limits > Output quota for /mynode count=-1,bytes=100 > Output stat for /mynode count=6,bytes=484 > [zk: localhost:2181(CONNECTED) 19] listquota /mynode_n > absolute path is /zookeeper/quota/mynode_n/zookeeper_limits > Output quota for /mynode_n count=2,bytes=-1 > Output stat for /mynode_n count=5,bytes=5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2180) quota do not take effect in version 3.4.6
seekerak created ZOOKEEPER-2180: --- Summary: quota do not take effect in version 3.4.6 Key: ZOOKEEPER-2180 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2180 Project: ZooKeeper Issue Type: Bug Environment: zookeeper version 3.4.6 Reporter: seekerak [zk: localhost:2181(CONNECTED) 18] listquota /mynode absolute path is /zookeeper/quota/mynode/zookeeper_limits Output quota for /mynode count=-1,bytes=100 Output stat for /mynode count=6,bytes=484 [zk: localhost:2181(CONNECTED) 19] listquota /mynode_n absolute path is /zookeeper/quota/mynode_n/zookeeper_limits Output quota for /mynode_n count=2,bytes=-1 Output stat for /mynode_n count=5,bytes=5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2096) C client builds with incorrect error codes in VisualStudio 2010+
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527709#comment-14527709 ] Ian Dimayuga commented on ZOOKEEPER-2096: - +1 [~fpj] have a look or point to relevant stakeholders? > C client builds with incorrect error codes in VisualStudio 2010+ > > > Key: ZOOKEEPER-2096 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2096 > Project: ZooKeeper > Issue Type: Bug > Components: build, c client > Environment: Windows MSVS 2010+ >Reporter: Vitaly Stakhovsky > Attachments: ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch, > ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > It reports: > warning C4005: 'EWOULDBLOCK' : macro redefinition > warning C4005: 'EINPROGRESS' : macro redefinition > In MSVS 2010+, these constants are now in . > What's worse, they have different numeric values. > Possible fix: > In "src/c/include/winconfig.h" : > #if _MSC_VER < 1600 > #define EWOULDBLOCK WSAEWOULDBLOCK > #define EINPROGRESS WSAEINPROGRESS > #endif -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2096) C client builds with incorrect error codes in VisualStudio 2010+
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Stakhovsky updated ZOOKEEPER-2096: - Attachment: ZOOKEEPER-2096.patch Done as advised > C client builds with incorrect error codes in VisualStudio 2010+ > > > Key: ZOOKEEPER-2096 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2096 > Project: ZooKeeper > Issue Type: Bug > Components: build, c client > Environment: Windows MSVS 2010+ >Reporter: Vitaly Stakhovsky > Attachments: ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch, > ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > It reports: > warning C4005: 'EWOULDBLOCK' : macro redefinition > warning C4005: 'EINPROGRESS' : macro redefinition > In MSVS 2010+, these constants are now in . > What's worse, they have different numeric values. > Possible fix: > In "src/c/include/winconfig.h" : > #if _MSC_VER < 1600 > #define EWOULDBLOCK WSAEWOULDBLOCK > #define EINPROGRESS WSAEINPROGRESS > #endif -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2040) Server to log underlying cause of SASL connection problems
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527516#comment-14527516 ] Hadoop QA commented on ZOOKEEPER-2040: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12730241/ZOOKEEPER-2040.002.patch against trunk revision 1677529. +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/2677//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2677//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2677//console This message is automatically generated. > Server to log underlying cause of SASL connection problems > -- > > Key: ZOOKEEPER-2040 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2040 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.6 >Reporter: Steve Loughran > Attachments: ZOOKEEPER-2040-log-SASL-errors-001.patch, > ZOOKEEPER-2040.002.patch > > > When you have SASL connectivity problems, you spend time staring at logs > —ideally logs with stack traces. > ZK server can help here by including the stack traces when there is a SASL > auth problem, rather than just giving the text of the exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: ZOOKEEPER-2040 PreCommit Build #2677
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2040 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2677/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 363045 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/2677//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2677//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2677//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] 9233a691b8676cfcec4c24054e873592c5da1657 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:1732: exec returned: 1 Total time: 51 minutes 49 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2674 Archived 24 artifacts Archive block size is 32768 Received 6 blocks and 33649719 bytes Compression is 0.6% Took 13 sec Recording test results Description set: ZOOKEEPER-2040 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## All tests passed
Re: making CI a more pleasant experience
Another possibility for speeding up pre-commit runs might be to execute
JUnit tests in parallel. In build.xml, we'd specify the threads attribute
on the task to start multiple JUnit processes. This requires Ant
1.9.4.
https://ant.apache.org/manual/Tasks/junit.html
It's not as simple as just deploying Ant 1.9.4 and turning it on though.
We'd need to make sure that test suites are capable of running
concurrently. They'd need isolated working directories, port numbers,
etc. Right now, the PortAssignment class hands out port numbers that are
guaranteed to be unique within the same process, but not across multiple
processes. I just tried it locally, and many tests failed on bind
exceptions. (This is actually a potential problem already if multiple
ZooKeeper pre-commit runs execute concurrently on the same Jenkins host.)
I'll investigate if we can change tests to bind to ephemeral ports, which
would give us uniqueness across multiple processes.
--Chris Nauroth
On 5/3/15, 10:10 PM, "Patrick Hunt" wrote:
>I've pushed back on use of sleep in non-deterministic ways in the past. I
>think we do a reasonable job there, just grepping for sleep doesn't tell
>the story.
>
>Where you run into issues is when you
>
>do x
>sleep(500)
>check x was success
>
>Most of our use of sleep has migrated to
>
>do x
>for (1 to 120) // or check elapsed time and cap at some large number
> sleep(500) // make sufficiently small that you don't waste time waiting
>unnecessarily, but also not too short that you spin
> check x was success
>
>unless we were able to make due without a time bound at all - sometimes we
>migrate to a latch or something.
>
>Now it's been a while since I reviewed the tests, new code might have
>added
>some bad checks again, it's a tough one to stamp out entirely.
>
>Re tests taking too long, I can't seem to find the jira, but iirc Henry
>had
>created a jira around reducing the tick time for tests - that
>significantly
>reduced the setup time for quorum based tests - a big part of overall
>overhead. We should probably categorize our tests and run a subset outside
>of a nightly "full test run".
>
>Patrick
>
>On Sun, May 3, 2015 at 9:49 PM, Raúl Gutiérrez Segalés
>
>wrote:
>
>> Hi,
>>
>> On 3 May 2015 at 12:53, Chris Nauroth wrote:
>>
>> > ()
>> > 3. Tests are non-deterministic, such as by hard-coding a sleep time to
>> > wait for an asynchronous action to complete. The solutions usually
>> > involve providing hooks into lower-layer logic, such as to receive a
>> > callback from the asynchronous action, so that the test can be
>> > deterministic.
>> >
>>
>> Indeed:
>>
>> ~/src/zookeeper-svn/src/java/test/org/apache/zookeeper (master) ✔ git
>>grep
>> -i 'sleep(' | wc -l
>> 91
>>
>> Making runs shorter would be very helpful as well. Currently it just
>>takes
>> too long.
>>
>> Also, adding to what Patrick said, I'll take a closer look at the runs
>> reported at:
>>
>> https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/
>>
>> to have a better grasp of what's going on. Thanks!
>>
>>
>> -rgs
>>
Failed: ZOOKEEPER-2040 PreCommit Build #2676
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2040 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2676/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 362055 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 failed 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/2676//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2676//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2676//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] e31008f165a2911605b67cd906f50107af1e9bbc 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:1732: exec returned: 2 Total time: 46 minutes 19 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2674 Archived 7 artifacts Archive block size is 32768 Received 6 blocks and 366671 bytes Compression is 34.9% Took 8.4 sec Recording test results Description set: ZOOKEEPER-2040 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 5 tests failed. REGRESSION: org.apache.zookeeper.test.AsyncOpsTest.testAsyncCreateFailure_NoNode Error Message: Address already in use Stack Trace: java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:344) at sun.nio.ch.Net.bind(Net.java:336) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) at org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:687) at org.apache.zookeeper.server.ServerCnxnFactory.configure(ServerCnxnFactory.java:75) at org.apache.zookeeper.server.ServerCnxnFactory.createFactory(ServerCnxnFactory.java:152) at org.apache.zookeeper.server.ServerCnxnFactory.createFactory(ServerCnxnFactory.java:145) at org.apache.zookeeper.test.ClientBase.createNewServerInstance(ClientBase.java:383) at org.apache.zookeeper.test.ClientBase.startServer(ClientBase.java:462) at org.apache.zookeeper.test.ClientBase.setUp(ClientBase.java:455) at org.apache.zookeeper.test.AsyncOpsTest.setUp(AsyncOpsTest.java:48) REGRESSION: org.apache.zookeeper.test.AuthTest.testBadAuthNotifiesWatch Error Message: Address already in use Stack Trace: java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:344) at sun.nio.ch.Net.bind(Net.java:336) at sun.nio.ch.ServerS
[jira] [Commented] (ZOOKEEPER-2040) Server to log underlying cause of SASL connection problems
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527142#comment-14527142 ] Hadoop QA commented on ZOOKEEPER-2040: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12730241/ZOOKEEPER-2040.002.patch against trunk revision 1677529. +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 failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2676//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2676//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2676//console This message is automatically generated. > Server to log underlying cause of SASL connection problems > -- > > Key: ZOOKEEPER-2040 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2040 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.4.6 >Reporter: Steve Loughran > Attachments: ZOOKEEPER-2040-log-SASL-errors-001.patch, > ZOOKEEPER-2040.002.patch > > > When you have SASL connectivity problems, you spend time staring at logs > —ideally logs with stack traces. > ZK server can help here by including the stack traces when there is a SASL > auth problem, rather than just giving the text of the exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2040) Server to log underlying cause of SASL connection problems
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated ZOOKEEPER-2040:
-
Attachment: ZOOKEEPER-2040.002.patch
[~rgs], would you please consider including Steve's patch in the upcoming 3.4.7
release? It's a one-line change to a log message, and it can be very useful
while troubleshooting.
I'm uploading a patch v002 file. This just takes Steve's earlier patch and
regenerates it with the {{--no-prefix}} option to satisfy the ZooKeeper
test-patch.sh script. This patch file can apply to both trunk and branch-3.4.
> Server to log underlying cause of SASL connection problems
> --
>
> Key: ZOOKEEPER-2040
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2040
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
>Affects Versions: 3.4.6
>Reporter: Steve Loughran
> Attachments: ZOOKEEPER-2040-log-SASL-errors-001.patch,
> ZOOKEEPER-2040.002.patch
>
>
> When you have SASL connectivity problems, you spend time staring at logs
> —ideally logs with stack traces.
> ZK server can help here by including the stack traces when there is a SASL
> auth problem, rather than just giving the text of the exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2096) C client builds with incorrect error codes in VisualStudio 2010+
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526998#comment-14526998
]
Ian Dimayuga commented on ZOOKEEPER-2096:
-
Hi [~vvs],
Please add the guards as recommended above:
{code}
#ifndef EWOULDBLOCK
#define EWOULDBLOCK WSAEWOULDBLOCK
#endif
#ifndef EINPROGRESS
#define EINPROGRESS WSAEINPROGRESS
#endif
{code}
> C client builds with incorrect error codes in VisualStudio 2010+
>
>
> Key: ZOOKEEPER-2096
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2096
> Project: ZooKeeper
> Issue Type: Bug
> Components: build, c client
> Environment: Windows MSVS 2010+
>Reporter: Vitaly Stakhovsky
> Attachments: ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch,
> ZOOKEEPER-2096.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> It reports:
> warning C4005: 'EWOULDBLOCK' : macro redefinition
> warning C4005: 'EINPROGRESS' : macro redefinition
> In MSVS 2010+, these constants are now in .
> What's worse, they have different numeric values.
> Possible fix:
> In "src/c/include/winconfig.h" :
> #if _MSC_VER < 1600
> #define EWOULDBLOCK WSAEWOULDBLOCK
> #define EINPROGRESS WSAEINPROGRESS
> #endif
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2124) Allow Zookeeper version string to have underscore '_'
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526953#comment-14526953
]
Hadoop QA commented on ZOOKEEPER-2124:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12730211/zookeeper-rpm-spec-files.patch
against trunk revision 1677529.
+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 failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2675//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2675//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2675//console
This message is automatically generated.
> Allow Zookeeper version string to have underscore '_'
> -
>
> Key: ZOOKEEPER-2124
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2124
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Jerry He
>Assignee: Chris Nauroth
> Fix For: 3.4.7, 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-2124-branch-3.4.001.patch,
> ZOOKEEPER-2124.001.patch, zookeeper-rpm-spec-files.patch
>
>
> Using Bigtop or other RPM build for Zookeeper, there is a problem with using
> the hyphen '-' character in the version string:
> {noformat}
> [bigdata@bdvs1166 bigtop]$ gradle zookeeper-rpm
> :buildSrc:compileJava UP-TO-DATE
> :buildSrc:compileGroovy UP-TO-DATE
> :buildSrc:processResources UP-TO-DATE
> :buildSrc:classes UP-TO-DATE
> :buildSrc:jar UP-TO-DATE
> :buildSrc:assemble UP-TO-DATE
> :buildSrc:compileTestJava UP-TO-DATE
> :buildSrc:compileTestGroovy UP-TO-DATE
> :buildSrc:processTestResources UP-TO-DATE
> :buildSrc:testClasses UP-TO-DATE
> :buildSrc:test UP-TO-DATE
> :buildSrc:check UP-TO-DATE
> :buildSrc:build UP-TO-DATE
> :zookeeper_vardefines
> :zookeeper-download
> :zookeeper-tar
> Copy /home/bigdata/bigtop/dl/zookeeper-3.4.6-IBM-1.tar.gz to
> /home/bigdata/bigtop/build/zookeeper/tar/zookeeper-3.4.6-IBM-1.tar.gz
> :zookeeper-srpm
> error: line 64: Illegal char '-' in: Version: 3.4.6-IBM-1
> :zookeeper-srpm FAILED
> FAILURE: Build failed with an exception.
> * Where:
> Script '/home/bigdata/bigtop/packages.gradle' line: 462
> * What went wrong:
> Execution failed for task ':zookeeper-srpm'.
> > Process 'command 'rpmbuild'' finished with non-zero exit value 1
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> BUILD FAILED
> {noformat}
> Also, according to the
> [rpm-maven-plugin|http://mojo.codehaus.org/rpm-maven-plugin/ident-params.html]
> documentation:
> {noformat}
> version
> The version number to use for the RPM package. By default, this is the
> project version. This value cannot contain a dash (-) due to contraints in
> the RPM file naming convention. Any specified value will be truncated at the
> first dash
> release
> The release number of the RPM.
> Beginning with release 2.0-beta-2, this is an optional parameter. By default,
> the release will be generated from the modifier portion of the project
> version using the following rules:
> If no modifier exists, the release will be 1.
> If the modifier ends with SNAPSHOT, the timestamp (in UTC) of the build will
> be appended to end.
> All instances of '-' in the modifier will be replaced with '_'.
> If a modifier exists and does not end with SNAPSHOT, "_1" will be appended to
> end.
> {noformat}
> We should allow underscore '_' as part of the version string. e.g.
> 3.4.6_abc_1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: ZOOKEEPER-2124 PreCommit Build #2675
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2124 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2675/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 364660 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 failed 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/2675//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2675//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2675//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] fb9363affe255fb1c21d68342eb657a527c691a8 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:1732: exec returned: 2 Total time: 51 minutes 58 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2674 Archived 24 artifacts Archive block size is 32768 Received 6 blocks and 33575519 bytes Compression is 0.6% Took 14 sec Recording test results Description set: ZOOKEEPER-2124 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Updated] (ZOOKEEPER-2124) Allow Zookeeper version string to have underscore '_'
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated ZOOKEEPER-2124:
-
Attachment: zookeeper-rpm-spec-files.patch
ZOOKEEPER-2124-branch-3.4.001.patch
[~rgs], thank you for the commit. I'm attaching a branch-3.4 patch. The patch
command was able to apply the trunk patch with a bit of fuzzing, so the
differences in the branch-3.4 patch file are just cosmetic.
Just as a reminder, I had left an earlier comment explaining that the rpm build
doesn't fully work without also applying some spec file patches that had turned
up on the mailing list a while ago.
https://issues.apache.org/jira/browse/ZOOKEEPER-2124?focusedCommentId=14503481&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14503481
http://mail-archives.apache.org/mod_mbox/zookeeper-user/201212.mbox/%3c50d2d481.8010...@pt-consulting.eu%3E
I didn't include them in my original patch, because I wanted to make sure the
original author received credit. For reference, I'm attaching a separate patch
file that consolidates those spec file changes from the mailing list.
> Allow Zookeeper version string to have underscore '_'
> -
>
> Key: ZOOKEEPER-2124
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2124
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Jerry He
>Assignee: Chris Nauroth
> Fix For: 3.4.7, 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-2124-branch-3.4.001.patch,
> ZOOKEEPER-2124.001.patch, zookeeper-rpm-spec-files.patch
>
>
> Using Bigtop or other RPM build for Zookeeper, there is a problem with using
> the hyphen '-' character in the version string:
> {noformat}
> [bigdata@bdvs1166 bigtop]$ gradle zookeeper-rpm
> :buildSrc:compileJava UP-TO-DATE
> :buildSrc:compileGroovy UP-TO-DATE
> :buildSrc:processResources UP-TO-DATE
> :buildSrc:classes UP-TO-DATE
> :buildSrc:jar UP-TO-DATE
> :buildSrc:assemble UP-TO-DATE
> :buildSrc:compileTestJava UP-TO-DATE
> :buildSrc:compileTestGroovy UP-TO-DATE
> :buildSrc:processTestResources UP-TO-DATE
> :buildSrc:testClasses UP-TO-DATE
> :buildSrc:test UP-TO-DATE
> :buildSrc:check UP-TO-DATE
> :buildSrc:build UP-TO-DATE
> :zookeeper_vardefines
> :zookeeper-download
> :zookeeper-tar
> Copy /home/bigdata/bigtop/dl/zookeeper-3.4.6-IBM-1.tar.gz to
> /home/bigdata/bigtop/build/zookeeper/tar/zookeeper-3.4.6-IBM-1.tar.gz
> :zookeeper-srpm
> error: line 64: Illegal char '-' in: Version: 3.4.6-IBM-1
> :zookeeper-srpm FAILED
> FAILURE: Build failed with an exception.
> * Where:
> Script '/home/bigdata/bigtop/packages.gradle' line: 462
> * What went wrong:
> Execution failed for task ':zookeeper-srpm'.
> > Process 'command 'rpmbuild'' finished with non-zero exit value 1
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> BUILD FAILED
> {noformat}
> Also, according to the
> [rpm-maven-plugin|http://mojo.codehaus.org/rpm-maven-plugin/ident-params.html]
> documentation:
> {noformat}
> version
> The version number to use for the RPM package. By default, this is the
> project version. This value cannot contain a dash (-) due to contraints in
> the RPM file naming convention. Any specified value will be truncated at the
> first dash
> release
> The release number of the RPM.
> Beginning with release 2.0-beta-2, this is an optional parameter. By default,
> the release will be generated from the modifier portion of the project
> version using the following rules:
> If no modifier exists, the release will be 1.
> If the modifier ends with SNAPSHOT, the timestamp (in UTC) of the build will
> be appended to end.
> All instances of '-' in the modifier will be replaced with '_'.
> If a modifier exists and does not end with SNAPSHOT, "_1" will be appended to
> end.
> {noformat}
> We should allow underscore '_' as part of the version string. e.g.
> 3.4.6_abc_1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2096) C client builds with incorrect error codes in VisualStudio 2010+
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526624#comment-14526624 ] Vitaly Stakhovsky commented on ZOOKEEPER-2096: -- Not sure how to respond to this, so I put it here: This patch affects only Windows. It builds fine on MSVC++ 2010, 2013. And there were no complaints from automated builds. As for the runtime behavior, I can tell from experience that without this fix the code would not work at all. This could be established immediately should there be any automated tests for Windows. > C client builds with incorrect error codes in VisualStudio 2010+ > > > Key: ZOOKEEPER-2096 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2096 > Project: ZooKeeper > Issue Type: Bug > Components: build, c client > Environment: Windows MSVS 2010+ >Reporter: Vitaly Stakhovsky > Attachments: ZOOKEEPER-2096.patch, ZOOKEEPER-2096.patch, > ZOOKEEPER-2096.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > It reports: > warning C4005: 'EWOULDBLOCK' : macro redefinition > warning C4005: 'EINPROGRESS' : macro redefinition > In MSVS 2010+, these constants are now in . > What's worse, they have different numeric values. > Possible fix: > In "src/c/include/winconfig.h" : > #if _MSC_VER < 1600 > #define EWOULDBLOCK WSAEWOULDBLOCK > #define EINPROGRESS WSAEINPROGRESS > #endif -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk-WinVS2008 - Build # 1787 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1787/ ### ## 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\hudson3691297608868753949.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 5/4/2015 12:18:11 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:01.18 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-2124) Allow Zookeeper version string to have underscore '_'
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526542#comment-14526542
]
Hudson commented on ZOOKEEPER-2124:
---
SUCCESS: Integrated in ZooKeeper-trunk #2681 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2681/])
ZOOKEEPER-2124 Allow Zookeeper version string to have underscore '_'
(Chris Nauroth via rgs) (rgs:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1677529)
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/build.xml
* /zookeeper/trunk/src/contrib/zkpython/build.xml
> Allow Zookeeper version string to have underscore '_'
> -
>
> Key: ZOOKEEPER-2124
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2124
> Project: ZooKeeper
> Issue Type: Bug
>Affects Versions: 3.4.6
>Reporter: Jerry He
>Assignee: Chris Nauroth
> Fix For: 3.4.7, 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-2124.001.patch
>
>
> Using Bigtop or other RPM build for Zookeeper, there is a problem with using
> the hyphen '-' character in the version string:
> {noformat}
> [bigdata@bdvs1166 bigtop]$ gradle zookeeper-rpm
> :buildSrc:compileJava UP-TO-DATE
> :buildSrc:compileGroovy UP-TO-DATE
> :buildSrc:processResources UP-TO-DATE
> :buildSrc:classes UP-TO-DATE
> :buildSrc:jar UP-TO-DATE
> :buildSrc:assemble UP-TO-DATE
> :buildSrc:compileTestJava UP-TO-DATE
> :buildSrc:compileTestGroovy UP-TO-DATE
> :buildSrc:processTestResources UP-TO-DATE
> :buildSrc:testClasses UP-TO-DATE
> :buildSrc:test UP-TO-DATE
> :buildSrc:check UP-TO-DATE
> :buildSrc:build UP-TO-DATE
> :zookeeper_vardefines
> :zookeeper-download
> :zookeeper-tar
> Copy /home/bigdata/bigtop/dl/zookeeper-3.4.6-IBM-1.tar.gz to
> /home/bigdata/bigtop/build/zookeeper/tar/zookeeper-3.4.6-IBM-1.tar.gz
> :zookeeper-srpm
> error: line 64: Illegal char '-' in: Version: 3.4.6-IBM-1
> :zookeeper-srpm FAILED
> FAILURE: Build failed with an exception.
> * Where:
> Script '/home/bigdata/bigtop/packages.gradle' line: 462
> * What went wrong:
> Execution failed for task ':zookeeper-srpm'.
> > Process 'command 'rpmbuild'' finished with non-zero exit value 1
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> BUILD FAILED
> {noformat}
> Also, according to the
> [rpm-maven-plugin|http://mojo.codehaus.org/rpm-maven-plugin/ident-params.html]
> documentation:
> {noformat}
> version
> The version number to use for the RPM package. By default, this is the
> project version. This value cannot contain a dash (-) due to contraints in
> the RPM file naming convention. Any specified value will be truncated at the
> first dash
> release
> The release number of the RPM.
> Beginning with release 2.0-beta-2, this is an optional parameter. By default,
> the release will be generated from the modifier portion of the project
> version using the following rules:
> If no modifier exists, the release will be 1.
> If the modifier ends with SNAPSHOT, the timestamp (in UTC) of the build will
> be appended to end.
> All instances of '-' in the modifier will be replaced with '_'.
> If a modifier exists and does not end with SNAPSHOT, "_1" will be appended to
> end.
> {noformat}
> We should allow underscore '_' as part of the version string. e.g.
> 3.4.6_abc_1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2174) JUnit4ZKTestRunner logs test failure for all exceptions even if the test method is annotated with an expected exception.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526541#comment-14526541
]
Hudson commented on ZOOKEEPER-2174:
---
SUCCESS: Integrated in ZooKeeper-trunk #2681 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2681/])
ZOOKEEPER-2174 JUnit4ZKTestRunner logs test failure for all exceptions
JUnit4ZKTestRunner logs test failure for all exceptions, even if the test
method is annotated with an expected exception (Chris Nauroth via rgs). (rgs:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1677460)
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/src/java/test/org/apache/zookeeper/JUnit4ZKTestRunner.java
> JUnit4ZKTestRunner logs test failure for all exceptions even if the test
> method is annotated with an expected exception.
>
>
> Key: ZOOKEEPER-2174
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2174
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
>Reporter: Chris Nauroth
>Assignee: Chris Nauroth
>Priority: Minor
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2174-branch-3.4.004.patch,
> ZOOKEEPER-2174.001.patch, ZOOKEEPER-2174.002.patch, ZOOKEEPER-2174.003.patch,
> ZOOKEEPER-2174.004.patch
>
>
> {{JUnit4ZKTestRunner}} wraps JUnit test method execution, and if any
> exception is thrown, it logs a message stating that the test failed.
> However, some ZooKeeper tests are annotated with {{@Test(expected=...)}} to
> indicate that an exception is the expected result, and thus the test passes.
> The runner should be aware of expected exceptions and only log if an
> unexpected exception occurs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper_branch35_jdk7 - Build # 284 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/284/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 361617 lines...] [exec] Log Message Received: [2015-05-04 10:44:19,674:2125(0x2b10fe3b6540):ZOO_INFO@log_env@980: Client environment:host.name=pietas.apache.org] [exec] Log Message Received: [2015-05-04 10:44:19,674:2125(0x2b10fe3b6540):ZOO_INFO@log_env@987: Client environment:os.name=Linux] [exec] Log Message Received: [2015-05-04 10:44:19,674:2125(0x2b10fe3b6540):ZOO_INFO@log_env@988: Client environment:os.arch=3.13.0-36-lowlatency] [exec] Log Message Received: [2015-05-04 10:44:19,674:2125(0x2b10fe3b6540):ZOO_INFO@log_env@989: Client environment:os.version=#63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014] [exec] Log Message Received: [2015-05-04 10:44:19,674:2125(0x2b10fe3b6540):ZOO_INFO@log_env@997: Client environment:user.name=jenkins] [exec] Log Message Received: [2015-05-04 10:44:19,674:2125(0x2b10fe3b6540):ZOO_INFO@log_env@1005: Client environment:user.home=/home/jenkins] [exec] Log Message Received: [2015-05-04 10:44:19,674:2125(0x2b10fe3b6540):ZOO_INFO@log_env@1017: Client environment:user.dir=/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/test-cppunit] [exec] Log Message Received: [2015-05-04 10:44:19,674:2125(0x2b10fe3b6540):ZOO_INFO@zookeeper_init_internal@1060: Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 watcher=0x45d350 sessionId=0 sessionPasswd= context=0x7fffbd1115a0 flags=0] [exec] Log Message Received: [2015-05-04 10:44:19,675:2125(0x2b1100a45700):ZOO_INFO@check_events@2298: initiated connection to server [127.0.0.1:22181]] [exec] Log Message Received: [2015-05-04 10:44:19,677:2125(0x2b1100a45700):ZOO_INFO@check_events@2350: session establishment complete on server [127.0.0.1:22181], sessionId=0x101ae6d0cc2000f, negotiated timeout=1 ] [exec] : elapsed 1001 : OK [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server started : elapsed 10113 : OK [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1001 : OK [exec] Zookeeper_simpleSystem::testNullData : elapsed 1020 : OK [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1003 : OK [exec] Zookeeper_simpleSystem::testCreate : elapsed 1008 : OK [exec] Zookeeper_simpleSystem::testPath : elapsed 1012 : OK [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1036 : OK [exec] Zookeeper_simpleSystem::testPing : elapsed 17158 : OK [exec] Zookeeper_simpleSystem::testAcl : elapsed 1011 : OK [exec] Zookeeper_simpleSystem::testChroot : elapsed 3030 : OK [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper server started : elapsed 30276 : OK [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1018 : OK [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper server started ZooKeeper server started ZooKeeper server started : elapsed 14502 : OK [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper server started ZooKeeper server started ZooKeeper server started : elapsed 14463 : OK [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1026 : OK [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4511 : OK [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started : elapsed 4205 : OK [exec] Zookeeper_readOnly::testReadOnly : elapsed 4111 : OK [exec] /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/src/c/tests/TestReconfig.cc:183: Assertion: equality assertion failed [Expected: 1, Actual : 0] [exec] Failures !!! [exec] Run: 72 Failure total: 1 Failures: 1 Errors: 0 [exec] FAIL: zktest-mt [exec] == [exec] 1 of 2 tests failed [exec] Please report to u...@zookeeper.apache.org [exec] == [exec] make[1]: Leaving directory `/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build/test/test-cppunit' [exec] make[1]: *** [check-TESTS] Error 1 [exec] make: *** [check-am] Error 2 BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build.xml:1439: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build.xml:1399: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_jdk7/branch-3.5/build.xml:1409: exec returned: 2 Total time: 49 minutes 9 seconds Build step 'Invoke Ant' marked build as failure Archiving artifacts Sending artifact delta rel
ZooKeeper_branch34_jdk7 - Build # 876 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/876/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 215359 lines...] [junit] 2015-05-04 09:36:16,721 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2015-05-04 09:36:16,721 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2015-05-04 09:36:16,721 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2015-05-04 09:36:16,721 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@224] - NIOServerCnxn factory exited run method [junit] 2015-05-04 09:36:16,721 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2015-05-04 09:36:16,722 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2015-05-04 09:36:16,722 [myid:] - INFO [main:PrepRequestProcessor@760] - Shutting down [junit] 2015-05-04 09:36:16,722 [myid:] - INFO [main:SyncRequestProcessor@209] - Shutting down [junit] 2015-05-04 09:36:16,722 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2015-05-04 09:36:16,722 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited! [junit] 2015-05-04 09:36:16,723 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2015-05-04 09:36:16,723 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2015-05-04 09:36:16,724 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2015-05-04 09:36:16,725 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2015-05-04 09:36:16,725 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2015-05-04 09:36:16,726 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2015-05-04 09:36:16,726 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2015-05-04 09:36:16,726 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test6843164155218856259.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test6843164155218856259.junit.dir/version-2 [junit] 2015-05-04 09:36:16,729 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2015-05-04 09:36:16,730 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:50235 [junit] 2015-05-04 09:36:16,730 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:50235 [junit] 2015-05-04 09:36:16,730 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2015-05-04 09:36:16,731 [myid:] - INFO [Thread-4:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:50235 (no session established for client) [junit] 2015-05-04 09:36:16,731 [myid:] - INFO [main:JMXEnv@229] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2015-05-04 09:36:16,732 [myid:] - INFO [main:JMXEnv@246] - expect:InMemoryDataTree [junit] 2015-05-04 09:36:16,733 [myid:] - INFO [main:JMXEnv@250] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2015-05-04 09:36:16,733 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2015-05-04 09:36:16,733 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2015-05-04 09:36:16,733 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 10471 [junit] 2015-05-04 09:36:16,733 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20 [junit] 2015-05-04 09:36:16,733 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota [junit] 2015-05-04 09:36:16,734 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2015-05-04 09:36:16,806 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x14d1e487cd0 closed [junit] 2015-05-04 09:36:16,806 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2015-05-04 09:36:16,806 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@512] - EventThread shut down [junit] 2015-05-04 09:36:16,807 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221
[jira] [Created] (ZOOKEEPER-2179) Typo in Watcher.java
Eunchan Kim created ZOOKEEPER-2179: -- Summary: Typo in Watcher.java Key: ZOOKEEPER-2179 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2179 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.0, 3.4.5 Reporter: Eunchan Kim Priority: Trivial Fix For: 3.5.0, 3.4.5 at zookeeper/src/java/main/org/apache/zookeeper/Watcher.java, * implement. A ZooKeeper client will get various events from the ZooKeepr should be fixed to * implement. A ZooKeeper client will get various events from the ZooKeeper. (Zookeepr -> Zookeeper) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk-solaris - Build # 1021 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1021/ ### ## 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-05-04T08:32:18.202 +' U src/contrib/zkpython/build.xml U src/java/test/org/apache/zookeeper/JUnit4ZKTestRunner.java U CHANGES.txt U build.xml At revision 1677550 Updating http://svn.apache.org/repos/asf/hadoop/nightly at revision '2015-05-04T08:32:18.202 +' At revision 1677550 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/hudson4694310531116438386.sh /var/tmp/hudson4694310531116438386.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 # 1786 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/1786/ ### ## 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\hudson6736496004350305608.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 5/4/2015 9:23:32 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:06.15 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.
