Dear linaro devlopers
Thanks to good answers, it is going well.
I have a question.
Squad fetches the result of lava, the interval is too long.
This is true even if you reduce the poll interval of the backend setting
in SQUAD.
It will fetch at least 1 hour later.
I want to fetch interval 30 minutes.
Is there a solution?
thanks
suker
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.*
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.
Thanks
ChoongHyun Jeon.
Dear squad developer
I used to squad docker of https://github.com/Linaro/squad.
And squad system running in my localhost. LAVA too.
I want check the submit test for squad.
Using a python script submit_for_testing.py in
https://git.linaro.org/ci/job/configs.git
command is below :
python submit_for_testing.py --device-type abc-abc-abc --build-number no1
--lava-server https://192.168.1.20:9099 --qa-server http://192.168.1.70:8000
--qa-server-project remote-lava-prj --qa-server-team remote-lava-team
--test-plan lava-test-plan.yaml
response : "QA Reports submission failed"
What is that mean ?
Squad system setup missing or wrong command?
If that command are success respone, something show on squad explore?
Thanks
kchhero
--
*행동하지 않으면 변화는 없다*
Hi everyone,
I'm using LAVA at NXP and after talking with Neil and Milosz, I'd like to
use SQUAD.
I followed the instructions here
https://squad.readthedocs.io/en/latest/install.html
But when I try to run the command "squad", bash tells me the command is not
found.
I tried to run it through Python3 shell, but didn't work either.
Maybe I'm missing something obvious ?
Best regards,
Axel
Hi,
I just rolled out SQUAD 0.58 to production qa-reports.linaro.org. This
is more of a bugfix release so the changelog is pretty short:
* api:
- fix the /builds//report API
There were a couple of issues with the API. In detail:
- baseline parameter is now respected
- 'force' is now respected
- API doesn't crash when baseline is not None
There is still a problem with displaying the URL for the baseline.
It's unfortunately incorrect and it should be considered a known
issue. It doesn't affect the output stored in output_* fields. The fix
is almost ready and will be submitted for review shortly.
milosz
Hi,
We had an issue that tasks from one backend blocked tasks from other
backends. Maybe we can create as many queues as we have backends and
route the tasks to them? I'm not sure this is easy or even possible,
but just sending this idea out for comments.
milosz
Hello,
For Google Data Studio integration with SQUAD, I need to retrieve the
list of metrics for each project so I can let user select which project
and metric he would like to view in the studio. Something like this
here:
https://github.com/Linaro/squad/blob/master/squad/frontend/views.py#L447
only for all available projects for this user.
Any suggestions on the correct approach here? I was thinking just adding
a new API function in squad/api/views.py but I'd like an input on this
approach and/or other ideas are welcome.
Thanks,
--
Stevan Radaković | LAVA Engineer
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs
Hi,
Getting the output of 'email' API for the build usually takes a long
time. In some cases we're close to hitting the 30 seconds timeout. I
think the timeout is inevitable when there are a lot of results with
big number of changes. In order to avoid timeout, maybe the API
should do the work in background? This would work as follows
1. GET call to /api/builds/<id>/email
2. server creates a 'cashed report' object in database and returns URL
for it immediately to the user
3. in the background server adds a report generation task to the queue
4. using the URL received in 2) user is able to retrieve the final
results or check the progress
5. once the result is generated it can be a short lived object in the
database (removed after 1 day for example)
Is this the solution we should aim for? The downside is that it
requires active polling from the client side.
milosz
Hi,
Antonio proposed a patch that sets default data retention policy to
180 days. It can be changed for each project in qa-reports separately
(extended or shortened). We don't have an option to keep the data
forever. IMHO this is a good idea, but I wanted to ask whether you
have a need to keep your results forever.
The PR in question is here:
https://github.com/Linaro/squad/pull/370
milosz