Skip to content

feat(labs): add a mock lab details page - #2172

Draft
alanpeixinho wants to merge 2 commits into
kernelci:mainfrom
profusion:feat/lab-details-proposal
Draft

alanpeixinho wants to merge 2 commits into
kernelci:mainfrom
profusion:feat/lab-details-proposal

Conversation

@alanpeixinho

Copy link
Copy Markdown
Contributor

Summary

A lab row in the listing now opens a details page for that lab, using the same origin and time window. The page shows submission fill, distribution, and per-tree builds, boots, and tests.

Mock data only, from labDetailsMock.ts. Part of #2168.

Made with Cursor

Preview one lab from the listing with sample submission fill, distribution, and tree results.

Signed-off-by: Alan Peixinho <[email protected]>
@alanpeixinho

alanpeixinho commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor Author

Full page of the mock lab details.

lab-baylibre-full.png

@alanpeixinho

Copy link
Copy Markdown
Contributor Author

left a small mockup, so we can iterate on the design of the proposed lab details page, any feedback would be appreciated.
cc: @tales-aparecida @bhcopeland @minash-ti

@nuclearcat

Copy link
Copy Markdown
Member

IMHO data need to be sorted by priority. What people check daily and most often - current builds status, so it must be on top, and first page without scrolling must be that people come for - daily.
Then, submission fill and distribution - probably at bottom. But this is IMHO and i think important to have other opinions.

@alanpeixinho

Copy link
Copy Markdown
Contributor Author

IMHO data need to be sorted by priority. What people check daily and most often - current builds status, so it must be on top, and first page without scrolling must be that people come for - daily. Then, submission fill and distribution - probably at bottom. But this is IMHO and i think important to have other opinions.

@nuclearcat To be fair, I was struggling with defining what is more important here. But I think I am with you here, those two aggregated are probably better going to the bottom. I will change and update the screenshot.

Put the tree results first and leave submission fill as the last section.

Assisted-by: Cursor
Signed-off-by: Alan Peixinho <[email protected]>
@alanpeixinho

Copy link
Copy Markdown
Contributor Author

@nuclearcat Done. Build status is at the top. Distribution follows, and submission fill is last.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants