flaky test in travis?

[thinkingfish]

$ cd ../test && python -m unittest discover

F

======================================================================

FAIL: test_miss (integration.test_twemcache_basic.TwemcacheBasicTest)

----------------------------------------------------------------------

Traceback (most recent call last):

  File "/home/travis/build/twitter/pelikan/test/integration/test_twemcache_basic.py", line 7, in test_miss

    self.assertMetrics(('request_parse', 1), ('get', 1), ('get_key_miss', 1))

  File "/home/travis/build/twitter/pelikan/test/integration/base.py", line 40, in assertMetrics

    stats.get(k, None),

AssertionError: Expected request_parse to be 1, got 0 instead

----------------------------------------------------------------------

Ran 1 test in 0.005s

FAILED (failures=1)

The command "cd ../test && python -m unittest discover" exited with 1.

Done. Your build exited with 1.

This occurred for all tests last night, went away this morning, and has now returned.

[thinkingfish]

@seppo0010 This was what made me take out the integration tests earlier.

[seppo0010]

Oh, wow, that's surprising... The test successfully read "END" but metrics are still 0... may that be an actual bug in pelikan?

[thinkingfish]

But other times it succeeded (on travis), and it always runs fine locally. I've also manually ran the test sequence to make sure this particular metric was not 0.

[thinkingfish]

The same behavior returned on travis. I'm disabling integration test until I can figure out why.

[thinkingfish]

I have merged the partial value change because I have two other branches that depend on it, including more tests. Will prioritize getting those tests in.

[seppo0010]

I'm now surprised this actually worked certain times... see #139.

[thinkingfish]

Indeed. Curious.

But we should re-enable the test now that you fixed the bug :)

[seppo0010]

The test was reenabled in that PR. Close this issue, please (I cannot!).