Hi all,Finally, found the problem. For some reason, py27 has to wait a little bit longer for the elasticsearch instance to be up. I just let the functional setup code wait a little while.Problem solved. Amazing! :)Many thanks :)On Wed, Dec 12, 2018 at 11:37 AM Trinh Nguyen <dangtrinhnt@gmail.com> wrote:Trying to look through the logs of the last merged patch set [1] but nothing there. Is there any other places that I can look into?Thanks,On Wed, Dec 12, 2018 at 9:47 AM Trinh Nguyen <dangtrinhnt@gmail.com> wrote:Thank Jeremy. I will look into bindep.On Wed, Dec 12, 2018 at 12:04 AM Jeremy Stanley <fungi@yuggoth.org> wrote:On 2018-12-11 15:21:47 +0900 (+0900), Trinh Nguyen wrote:
> I'm trying to figure out how Zuul processes the test-setup.sh [1]
> file to adopt new dependencies.
[...]
Looking at what you've put in there for your JRE packages, those
would be better handled in a bindep.txt file in your repository.
Running tools/test-setup.sh in jobs is really to catch other sorts
of setup steps like precreating a database or formatting and
mounting a particular filesystem your tests are going to rely on.
For system package dependencies of your jobs, we have a declarative
mechanism already which doesn't require complex conditional
handling: we install whatever bindep says is missing.
I see you're also leveraging tools/test-setup.sh to obtain packages
of elasticsearch which are not available in the distributions on
which your jobs run, which I guess is a suitable workaround though
it seems odd to test on platforms which don't package the software
on which your project relies.
--
Jeremy Stanley
------