Enable --days switch for getting tree list

[JenySadadia]

For the command kci-dev results trees, add --days option to provide a period of time in days to
get results for.

Closes #176

[JenySadadia]

Hello @aliceinwire
The command gives 78 trees even if the number of days passed is 1.
Where the dashboard shows 25 trees when days selected is 1.
Looks like there is some issue with the dashboard API /api/trees-fast/.
Could you please help me to verify?

[JenySadadia]

Looks like an issue with the dashboard API.
Created kernelci/dashboard#1287

[aliceinwire]

thanks for this PR and finding a related bug on the dashboard api
will merge this after the dashboard update and be sure that it works correctly

[aliceinwire]

can you solve the branch conflict with kcidev/subcommands/results/parser.py by adding the missing logging part?

[JenySadadia]

can you solve the branch conflict with kcidev/subcommands/results/parser.py by adding the missing logging part?

Resolved the conflict.

[JenySadadia]

Also, the option interval_in_days only works when port number is specified.
Could you please explain the reason? @aliceinwire @nuclearcat
Do we have multiple instances running for dashboard APIs?

[aliceinwire]

as is using the dashboard api, could this be a dashboard problem?

[aliceinwire]

I doubt that adding a interval_in_days fetch parameters justify the necessity of specify the port number

[aliceinwire]

by the way I tested on my side without specify the port parameters and works correctly

DASHBOARD_API = "https://dashboard.kernelci.org/api/"

[JenySadadia]

So do you mean output differs for $ kci-dev --settings ./kci-dev.toml results trees --days 1 and $ kci-dev --settings ./kci-dev.toml results trees --days 7
It doesn't in my case.

[aliceinwire]

So do you mean output differs for $ kci-dev --settings ./kci-dev.toml results trees --days 1 and $ kci-dev --settings ./kci-dev.toml results trees --days 7 It doesn't in my case.

I see. That's the same result also on my side.

[JenySadadia]

Yes, it only differs with the port number specified.
Need to ask on the dashboard repo.

[aliceinwire]

@JenySadadia thanks

[padovan]

9000 is our staging/dev instance https://staging.dashboard.kernelci.org:9000/
so code lands there first and you will get different behavior from the prod instance often times.

[JenySadadia]

9000 is our staging/dev instance https://staging.dashboard.kernelci.org:9000/ so code lands there first and you will get different behavior from the prod instance often times.

The URL is https://dashboard.kernelci.org. I think that's the production one.

[aliceinwire]

we should have DASHBOARD_API not hardcoded but added to the .kci-dev.toml.example and defaulted to something

[JenySadadia]

@aliceinwire This PR is ready to be merged. Could you please approve/create a suggestion?