Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[libbeat] Flaky test test_base.Test.test_persistent_uuid #9216

Closed
jsoriano opened this issue Nov 23, 2018 · 0 comments
Closed

[libbeat] Flaky test test_base.Test.test_persistent_uuid #9216

jsoriano opened this issue Nov 23, 2018 · 0 comments
Assignees
@ph
Labels
flaky-test Unstable or unreliable test cases. libbeat

Comments

@jsoriano
Copy link
Member

Flaky Test

Stack Trace

Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/private/var/lib/jenkins/workspace/elastic+beats+pull-request+multijob-darwin/beat/libbeat/label/macosx/src/github.com/elastic/beats/libbeat/tests/system/test_base.py", line 206, in test_persistent_uuid
    meta1 = run()
  File "/private/var/lib/jenkins/workspace/elastic+beats+pull-request+multijob-darwin/beat/libbeat/label/macosx/src/github.com/elastic/beats/libbeat/tests/system/test_base.py", line 188, in run
    max_timeout=2)
  File "/private/var/lib/jenkins/workspace/elastic+beats+pull-request+multijob-darwin/beat/libbeat/label/macosx/src/github.com/elastic/beats/libbeat/tests/system/beat/beat.py", line 337, in wait_until
    "Waited {} seconds.".format(max_timeout))
TimeoutError: Timeout waiting for 'cond' to be true. Waited 2 seconds.
@jsoriano jsoriano added libbeat flaky-test Unstable or unreliable test cases. labels Nov 23, 2018
@jsoriano jsoriano mentioned this issue Nov 23, 2018
Merged
@urso urso assigned ph Feb 8, 2019
@ph ph mentioned this issue Feb 11, 2019
Merged
ph added a commit to ph/beats that referenced this issue Feb 12, 2019
@ph
Give more times to check for Mockbet alive
bdbdacb 
Under darwin that test was flaky, I've ran it a few times locally
without issues. looking at the previous issue we always fails check that
Mockbeat is alived, but since this run on VM, we could hit contention
issues with either disk or cpu. Lets give more time to actually assert
before timeout.

Fixes: elastic#9216
@ph ph closed this as completed in #10680 Feb 12, 2019
ph added a commit that referenced this issue Feb 12, 2019
@ph
Give more times to check for Mockbet alive (#10680)
36a7cb0 
Under darwin that test was flaky, I've ran it a few times locally
without issues. looking at the previous issue we always fails check that
Mockbeat is alived, but since this run on VM, we could hit contention
issues with either disk or cpu. Lets give more time to actually assert
before timeout.

Fixes: #9216
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ph ph

Labels
flaky-test Unstable or unreliable test cases. libbeat
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ph @jsoriano