Today we talked about getting a regression report out of https://qa-reports.linaro.org/android-lkft/aosp-master-tracking/
I gave this url, which seems useful: https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
To get that URL, I did this: - In the API, navigated to: - https://qa-reports.linaro.org/api/, then 'projects' - from https://qa-reports.linaro.org/api/projects, found aosp-master-tracking - from https://qa-reports.linaro.org/api/projects/116, found 'builds' - from https://qa-reports.linaro.org/api/projects/116/builds/, I chose build 13703 (version 1129) - from https://qa-reports.linaro.org/api/builds/13703/, generate a report. Once a report is generated, display inline as an email.
The documentation is helpful at this point, and is available at https://squad.readthedocs.io/en/latest/api.html#reports-api-reports and also under "email" at https://squad.readthedocs.io/en/latest/api.html#builds-api-builds
So given build '13703', I requested a report by appending "report/?baseline=13670": https://qa-reports.linaro.org/api/builds/13703/report/?baseline=13670
At this point, a callback url is given and the report generation happens asynchronously. Once completed, the report is stored in json format at the callback url. In this case: https://qa-reports.linaro.org/api/reports/187/
The subtle thing here is that the report can be viewed by using the email interface with the same arguments. https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
So in summary: https://qa-reports.linaro.org -> https://qa-reports.linaro.org/api/ -> https://qa-reports.linaro.org/api/projects -> https://qa-reports.linaro.org/api/projects/116 -> https://qa-reports.linaro.org/api/projects/116/builds/ -> https://qa-reports.linaro.org/api/builds/13703/ -> https://qa-reports.linaro.org/api/builds/13703/report/?baseline=13670 -> (wait a couple minutes) https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
I guess it's a bit to bite off manually, but it's easy to automate. To that end, I think you'll get automated reports if you can convince your builds to "finish". I set expected test runs to 0 for all environments, in hopes that will help. The rest of the project settings looked fine to me already.
Dan
Thanks for pulling this all together Dan. There’s a lot of useful institutional knowledge here that when strung together yields something pretty useful.
Time for a little python or maybe an Android app. :-D
On Feb 19, 2019, at 11:40 AM, Dan Rue dan.rue@linaro.org wrote:
Today we talked about getting a regression report out of https://qa-reports.linaro.org/android-lkft/aosp-master-tracking/
I gave this url, which seems useful: https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
To get that URL, I did this:
- In the API, navigated to:
- https://qa-reports.linaro.org/api/, then 'projects'
- from https://qa-reports.linaro.org/api/projects, found aosp-master-tracking
- from https://qa-reports.linaro.org/api/projects/116, found 'builds'
- from https://qa-reports.linaro.org/api/projects/116/builds/, I chose build 13703 (version 1129)
- from https://qa-reports.linaro.org/api/builds/13703/, generate a report. Once a report is generated, display inline as an email.
The documentation is helpful at this point, and is available at https://squad.readthedocs.io/en/latest/api.html#reports-api-reports and also under "email" at https://squad.readthedocs.io/en/latest/api.html#builds-api-builds
So given build '13703', I requested a report by appending "report/?baseline=13670": https://qa-reports.linaro.org/api/builds/13703/report/?baseline=13670
At this point, a callback url is given and the report generation happens asynchronously. Once completed, the report is stored in json format at the callback url. In this case: https://qa-reports.linaro.org/api/reports/187/
The subtle thing here is that the report can be viewed by using the email interface with the same arguments. https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
So in summary: https://qa-reports.linaro.org -> https://qa-reports.linaro.org/api/ -> https://qa-reports.linaro.org/api/projects -> https://qa-reports.linaro.org/api/projects/116 -> https://qa-reports.linaro.org/api/projects/116/builds/ -> https://qa-reports.linaro.org/api/builds/13703/ -> https://qa-reports.linaro.org/api/builds/13703/report/?baseline=13670 -> (wait a couple minutes) https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
I guess it's a bit to bite off manually, but it's easy to automate. To that end, I think you'll get automated reports if you can convince your builds to "finish". I set expected test runs to 0 for all environments, in hopes that will help. The rest of the project settings looked fine to me already.
Dan
On Tue, 19 Feb 2019 at 17:41, Dan Rue dan.rue@linaro.org wrote:
Today we talked about getting a regression report out of https://qa-reports.linaro.org/android-lkft/aosp-master-tracking/
I gave this url, which seems useful: https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
To get that URL, I did this:
- In the API, navigated to:
- https://qa-reports.linaro.org/api/, then 'projects'
- from https://qa-reports.linaro.org/api/projects, found aosp-master-tracking
- from https://qa-reports.linaro.org/api/projects/116, found 'builds'
- from https://qa-reports.linaro.org/api/projects/116/builds/, I chose build 13703 (version 1129)
you can also do: https://qa-reports.linaro.org/api/projects/116/builds/?version=1129 For some reason this doesn't work although it should. I'll check when I'm back after holidays.
I guess it might also be useful to give the API link in the build view: https://qa-reports.linaro.org/android-lkft/aosp-master-tracking/build/1129/ I thought about that before but never got to do it. Please let me know if it would be useful?
milosz
- from https://qa-reports.linaro.org/api/builds/13703/, generate a report. Once a report is generated, display inline as an email.
The documentation is helpful at this point, and is available at https://squad.readthedocs.io/en/latest/api.html#reports-api-reports and also under "email" at https://squad.readthedocs.io/en/latest/api.html#builds-api-builds
So given build '13703', I requested a report by appending "report/?baseline=13670": https://qa-reports.linaro.org/api/builds/13703/report/?baseline=13670
At this point, a callback url is given and the report generation happens asynchronously. Once completed, the report is stored in json format at the callback url. In this case: https://qa-reports.linaro.org/api/reports/187/
The subtle thing here is that the report can be viewed by using the email interface with the same arguments. https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
So in summary: https://qa-reports.linaro.org -> https://qa-reports.linaro.org/api/ -> https://qa-reports.linaro.org/api/projects -> https://qa-reports.linaro.org/api/projects/116 -> https://qa-reports.linaro.org/api/projects/116/builds/ -> https://qa-reports.linaro.org/api/builds/13703/ -> https://qa-reports.linaro.org/api/builds/13703/report/?baseline=13670 -> (wait a couple minutes) https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
I guess it's a bit to bite off manually, but it's easy to automate. To that end, I think you'll get automated reports if you can convince your builds to "finish". I set expected test runs to 0 for all environments, in hopes that will help. The rest of the project settings looked fine to me already.
Dan
On Wed, 20 Feb 2019 at 08:18, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Tue, 19 Feb 2019 at 17:41, Dan Rue dan.rue@linaro.org wrote:
Today we talked about getting a regression report out of https://qa-reports.linaro.org/android-lkft/aosp-master-tracking/
I gave this url, which seems useful: https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
To get that URL, I did this:
- In the API, navigated to:
- https://qa-reports.linaro.org/api/, then 'projects'
- from https://qa-reports.linaro.org/api/projects, found aosp-master-tracking
- from https://qa-reports.linaro.org/api/projects/116, found 'builds'
- from https://qa-reports.linaro.org/api/projects/116/builds/, I chose build 13703 (version 1129)
you can also do: https://qa-reports.linaro.org/api/projects/116/builds/?version=1129 For some reason this doesn't work although it should. I'll check when I'm back after holidays.
This filter works: https://qa-reports.linaro.org/api/builds/?version=1129&project=116
milosz
I guess it might also be useful to give the API link in the build view: https://qa-reports.linaro.org/android-lkft/aosp-master-tracking/build/1129/ I thought about that before but never got to do it. Please let me know if it would be useful?
milosz
- from https://qa-reports.linaro.org/api/builds/13703/, generate a report. Once a report is generated, display inline as an email.
The documentation is helpful at this point, and is available at https://squad.readthedocs.io/en/latest/api.html#reports-api-reports and also under "email" at https://squad.readthedocs.io/en/latest/api.html#builds-api-builds
So given build '13703', I requested a report by appending "report/?baseline=13670": https://qa-reports.linaro.org/api/builds/13703/report/?baseline=13670
At this point, a callback url is given and the report generation happens asynchronously. Once completed, the report is stored in json format at the callback url. In this case: https://qa-reports.linaro.org/api/reports/187/
The subtle thing here is that the report can be viewed by using the email interface with the same arguments. https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
So in summary: https://qa-reports.linaro.org -> https://qa-reports.linaro.org/api/ -> https://qa-reports.linaro.org/api/projects -> https://qa-reports.linaro.org/api/projects/116 -> https://qa-reports.linaro.org/api/projects/116/builds/ -> https://qa-reports.linaro.org/api/builds/13703/ -> https://qa-reports.linaro.org/api/builds/13703/report/?baseline=13670 -> (wait a couple minutes) https://qa-reports.linaro.org/api/builds/13703/email/?baseline=13670
I guess it's a bit to bite off manually, but it's easy to automate. To that end, I think you'll get automated reports if you can convince your builds to "finish". I set expected test runs to 0 for all environments, in hopes that will help. The rest of the project settings looked fine to me already.
Dan
-
Dan Rue -
Milosz Wasilewski -
Tom Gall