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 &
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?
I attached the qemu01.yaml used for the test.
thanks
suker
On 19. 1. 8. 오후 8:40, Milosz Wasilewski wrote:
On Tue, 8 Jan 2019 at 11:21, suker suker@nexell.co.kr wrote:
Dear Milosz
I am sorry for repeated questions. Your answers are helpful in a variety of ways.
I went back to the beginning. To build a squad system, use 'git clone https://github.com/Linaro/squad'
I received a clone of github's squad. I modified the dev-docker slightly to suit my server environment.
could you list your changes here?
Using submit_for_testing.py as in the configuration at https://ci.linaro.org submit. Is there anything wrong with what I've done so far?
No, looks OK. However if you didn't add it to dockerfile you're only running frontend at this point. Which means...
I have additional questions. Should I use https protocol instead of http protocol? I traced at the source level using pdb, Eventually there will not get out of the loop at
/usr/local/lib/python3.5/dist-packages/kombu/utils/functional.py(341) retry_over_time()
And it appears to be connection refused (*** ConnectionRefusedError: [Errno 111] Connection refused) at
/usr/local/lib/python3.5/dist-packages/kombu/connection.py
... you're not able to connect to the message queue and workers. This is what this error is about. In our production instance we're using RabbitMQ as message queue. If you plan to use sth else you'll need to modify squad settings as well.
So to recover you need to make sure you're running:
- squad frontend
- squad worker (celery)
- rabbitmq
- squad listener (optional, but required for prompt result retrieval from LAVA)
I hope this helps.
milosz
thanks
suker
On 18. 12. 12. 오후 7:34, Milosz Wasilewski wrote:
On Wed, 12 Dec 2018 at 08:09, suker suker@nexell.co.kr wrote:
Dear linaro
I am a software engineer and working for Nexell Corporation in South Korea.
Recently, I found SQUAD and interested.
I downloaded the source from github and tried to run the docker and it on the local machine.
Unfortunately, SQUAD admistration is complicated and the setting method is unknown.
For example, to connect with Jenkins and SQUAD, *I do not know how to set it in SQUAD.*
Could you describe your goal here? SQUAD is a tool to collect testing results. I'm not sure what do you mean by 'connect Jenkins to SQUAD'. There may be many ways and it depends on your use case.
Already I saw below page.
(https://squad.readthedocs.io/en/latest/api.html#projects-api-projects)
Jenkins and LAVA are already in operation in my company.
if you're planning to use jenkins for building and LAVA for testing, SQUAD can be used to track results of the tests. We have similar setup at Linaro. In short jenkins build scripts generate LAVA job definitions. Than these definitions are send to SQUAD so it can submit them to LAVA and track the test jobs. After test jobs are completed results are pulled from LAVA. Here is example script from our jenkins build: https://git.linaro.org/ci/job/configs.git/tree/openembedded-lkft/submit_for_... as you can see the SQUAD API to call in this case is /api/submitjob. Details about it here in the docs: https://squad.readthedocs.io/en/latest/ci.html#ci-job-ref-label
milosz
Thanks
ChoongHyun Jeon.
Squad-dev mailing list Squad-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/squad-dev