Hey all,
I've opened:
https://issues.apache.org/jira/browse/SAMZA-576
Likely some timing issue in the test with Kafka. This test is really an
integration test, masquerading as a JUnit test. We should investigate and
fix.
Cheers,
Chris
On Wed, Feb 25, 2015 at 10:39 AM, Yi Pan wrote:
> Hi, M
Hi, Milinda,
I have seen a similar intermittent test failure on my boxes as well, just
did not have time to dig into it yet. It seems to be a timing issue in the
unit test.
Could you open a JIRA s.t. we don't forget it?
-Yi
On Wed, Feb 25, 2015 at 6:54 AM, Milinda Pathirage
wrote:
> Hi Chris,
Hi Chris,
I think above is a intermittent issue. When I ran ./bin/check-all.sh this
morning, it worked.
Thanks
Milinda
On Wed, Feb 25, 2015 at 2:34 AM, Chris Riccomini
wrote:
> Hey Milinda,
>
> No, I haven't seen this fail. Is this transient or does it happen every
> time? I ran a bin/check-al
Hey Milinda,
No, I haven't seen this fail. Is this transient or does it happen every
time? I ran a bin/check-all.sh after the merge this morning, and didn't see
any failures.
Cheers,
Chris
On Tuesday, February 24, 2015, Milinda Pathirage
wrote:
> Hi Devs,
>
> Has anyone seen following test fai
Hi Devs,
Has anyone seen following test failure:
testShouldGetOldestNewestAndNextOffsets FAILED
java.lang.AssertionError: expected:<0> but was:
at org.junit.Assert.fail(Assert.java:91)
at org.junit.Assert.failNotEquals(Assert.java:645)
at org.junit.Assert.assertEqu
