Hi Clark, Outputting the exec logs does help. And, I found the problem for the functional tests to fail, it because ES cannot be started because of the way the functional sets up the new version of ES server (5.x). I'm working on updating it. Many thanks, On Tue, Dec 4, 2018 at 1:39 AM Clark Boylan <cboylan@sapwetik.org> wrote:
On Mon, Dec 3, 2018, at 7:28 AM, Trinh Nguyen wrote:
Hello,
Currently, [1] fails tox py27 tests on Zuul check for just updating the log text. The tests are successful at local dev env. Just wondering there is any new change at Zuul CI?
Reading the exceptions [2] and the test setup code [3] it appears that elasticsearch isn't responding on its http port and is thus treated as having not started. With the info we currently have it is hard to say why. Instead of redirecting exec logs to /dev/null [4] maybe we can capture that data? Also probably worth grabbing the elasticsearch daemon log as well.
Without that information it is hard to say why this happened. I am not aware of any changes in the CI system that would cause this, but we do rebuild our test node images daily.
[2] http://logs.openstack.org/62/619162/5/check/openstack-tox-py27/9ce318d/job-o... [3] https://git.openstack.org/cgit/openstack/searchlight/tree/searchlight/tests/... [4] https://git.openstack.org/cgit/openstack/searchlight/tree/searchlight/tests/...
Clark
-- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*