On Wed, Jan 09, 2019 at 05:21:14PM +0900, suker wrote:
Dear Milosz and Antonio
Thank you for your response. It has been a great help.
As your advice, run the service in the following order.
$squad --bind 0.0.0.0:5000 &> /dev/null & $ sudo rabbitmq-server &> /dev/null & $ celery -A squad worker &> /dev/null & $ celery -A squad beat &> /dev/null & $ squad-admin listen &> /dev/null &
the problem with `&> /dev/null &` is that you have no way of debugging because you are thworing away all the logs. I suggest you run each of those in a separate terminal, in the foreground, while you are debugging.
It disappears connection problem and it seems to work well. And itcan also submit to lava-server.
But, very sorry, I have another question. On the testjobs page, I do not know what 'Not fetched' means.
And I do not see the test results in the build summary, test.yaml file is incomplete?
nor lava does not response?
It means the test results were not fetched from lava yet, and that is why no results are displayed.
when the squad listener (`squad-admin listen`) receives a notification from the lava zmq notifier (when enabled in lava), tests jobs are fetched right away when finished. Otherwise, the squad worker will fetch new finished test jobs from lava periodically (default: every 60 minutes, i.e. 1 hour).