[
https://issues.apache.org/jira/browse/AVRO-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211699#comment-14211699
]
David Laxer commented on AVRO-1602:
-----------------------------------
$ ./build.sh test
…
[py-test] java -jar
/Users/davidlaxer/avro/lang/java/tools/target/avro-tools-1.8.0-SNAPSHOT.jar
tether --in /tmp/test_tether_word_count/in --out
/tmp/test_tether_word_count/out --outschema
/var/folders/nj/nphdkhyj6s1dttb0pd9zb2wc0000gn/T/wordcountPQjDgE.avsc
--protocol http --program
/var/folders/nj/nphdkhyj6s1dttb0pd9zb2wc0000gn/T/exec_word_count_xhDecz
BUILD SUCCESSFUL
Total time: 11 minutes 13 seconds
+ cd lang/py3
+ python3 setup.py test
./build.sh: line 45: python3: command not found
> FAILURE! - in org.apache.avro.ipc.trace.TestFileSpanStorage
> -----------------------------------------------------------
>
> Key: AVRO-1602
> URL: https://issues.apache.org/jira/browse/AVRO-1602
> Project: Avro
> Issue Type: Bug
> Components: build
> Affects Versions: 1.7.7
> Environment: Mac OS X 10.10 Yosemite
> Reporter: David Laxer
> Assignee: Doug Cutting
> Fix For: 1.8.0
>
> Attachments: AVRO-1602-1.patch, Screen Shot 2014-11-10 at 9.01.12
> AM.png
>
>
> Running org.apache.avro.ipc.trace.TestFileSpanStorage
> Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.995 sec <<<
> FAILURE! - in org.apache.avro.ipc.trace.TestFileSpanStorage
> testRangeQuery1(org.apache.avro.ipc.trace.TestFileSpanStorage) Time elapsed:
> 0.363 sec <<< FAILURE!
> java.lang.AssertionError: expected:<8> but was:<4>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.avro.ipc.trace.TestFileSpanStorage.testRangeQuery1(TestFileSpanStorage.java:159)
> I see this issue:
> http://apache-avro.679487.n3.nabble.com/Build-failed-in-Jenkins-AvroJava-475-td4030947.html
> Is there a work-around?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
