Re: KernelCI Dashboard - Hardware Listing Behavior

--VpV/i2Wg9+mMBAWH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 22, 2026 at 11:17:46AM +0000, Chris Paterson wrote:
> > From: Gustavo Flores <[email protected]>

> > 2. Show tests from the most recent checkout in which each specific
> > hardware was tested, even if it's not the latest checkout of a tree.

> I'm not sure Option 2 would work so well if there are more than one check=
out on different trees testing the same board in similar timeframes.
> Say linux-stable and linux-next pipelines are kicked off at the same time.
> The linux-stable checkout may finish a hour earlier having failures, then=
 an hour latest linux-next finished and we can no longer see the "latest ba=
d" result from linux-stable.=20

Right, the most recent commit in development terms may not be the most
recent commit tested.  I think what we probably want for this option is
to have a report showing the most recent state for a series of specific
trees, for example mainline, next and all the stables where there are
results for the specific board.  I think that's more likely to show
people the state they're interested in.

--VpV/i2Wg9+mMBAWH
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmlyJNYACgkQJNaLcl1U
h9CW2Qf+J2wA/yzAqF6fh1AdAhFfjLvFbpznS14mVGGxujVuCZPGtQdcQ6nfEp0E
fIbQ/LN/O4heywWdlC1rvEFcHexWzVwFBU52hR4d0m0tQUKQlBGGlzvk1fy09HF5
NavxCYGQRgATbn5KqTTR65m4AMJttBk9/o/Y9lGM6NIUpqlX6lRXxJAe0245+g5w
VaxGv3FFXQaBxZlxTZDUfmgPZ3DYiKArrTjJyNq6WON5cczxMru0LgFz174qFH0K
SMKAlwUYrSgt2etgQXL+5kRRh2ZdgImo/mCMkSeSLA+ol2pwZflUZ6xxkskkMKQt
KjxmcV2qpTCIZrKuI6RcjilhoWrbHw==
=QoVo
-----END PGP SIGNATURE-----

--VpV/i2Wg9+mMBAWH--