Hardware missing from Hardware table

[bhcopeland]

From discord:

Ben Copeland — Yesterday at 17:24
How come https://dashboard.kernelci.org/tree/mainline/master/8cdeaa50eae8dad34885515f62559ee83e7e8dda?df%7Ch%7Cexynos850-e850-96=true&o=linaro_pull_labs&p=bt no longer shows up on hardware? It used to, when I search https://dashboard.kernelci.org/hardware?hs=exynos850 on hardware I get no results anymore

Tales — Yesterday at 18:04
some quirk with origin filtering maybe? linaro_pull_labs in the build and test getting dropped from the search? It appears when using the new filters, so I don't think it's not present in the table https://dashboard.kernelci.org/hardware?ch=8cdeaa50eae8dad34885515f62559ee83e7e8dda&gb=master&gu=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git&t=mainline

Let me know if you want any more details

[alanpeixinho]

@bhcopeland @tales-aparecida
There seems to be two problems here:

1. linaro_pull_labs missing from Hardware origin dropdown
   Hardware uses a hardcoded test_origins list. That list never included linaro_pull_labs, so you could not select it there (Tree can, because it uses live checkout origins).
2. Default Hardware listing only shows latest checkout
   It joins hardware_status to latest_checkout. If a board was tested on an older tip but not the newest one, it disappears.

This seems to be a behavior prior to the revision filter on the hardware listing. But I believe we can solve this by

1. Making origins dynamic.
2. Showing tests from a time window (instead of limiting for the latest checkout of a tree) -- I will investigate if this is viable performance-wise.

[mentonin]

If performance is an issue, we can add a new table analogous to latest_checkout, but for hardware platforms (latest_checkout maps tree to checkout, latest_checkout_by_platform would map platform to checkout)

[alanpeixinho]

This issue is similar to described on #1705 (hardware listing omit hardware not tested on latest checkout) and #1264 (when clicking to open hardware details for hardware not tested on latest checkout)

[alanpeixinho]

If performance is an issue, we can add a new table analogous to latest_checkout, but for hardware platforms (latest_checkout maps tree to checkout, latest_checkout_by_platform would map platform to checkout)

Turns out, hardware_status aggregation already brings us checkout_id without a full scan on tests table, so I believe we are covered on this regard.